The Moxie.cfg file is read on server start and controls aspects that cannot be changed while the server is running.
The optional Moxie.http file is read on server start and controls the default HTTP headers set for all requests.
Download Free Download of Moxie.Build Delivered as a simple .zip file, so that you can set it up however you like. This approach allows you to custom install many services on one server ,
or just run it as an app without an install. Licensing information and agreement . Upgrade Notes
In order to Upgrade an existing copy of Moxie.Build V4 or V5 to the most recent version of V5, you can use the Upgrade example files found in the Tools folder to help automate upgrading multi-service systems, or you can just replace the following files/folders: Moxie.exe Moxie.dll Default.dll /DBStore/BuiltIn.* /Lib /Public/BuiltIn /Templates/Admin /Templates/Clean /Templates/Default /Templates/Default5 /Templates/Report
Moxie.Build Keeps it Simple The full stack in one app, delivered by one company. Coding with the MOX server side scripting language is concise, well structured, and keeps your focus on the data. Use Moxie.Build in your company to pull together resources, centralize data, customize business workflows, and act as a highly accessible web portal for staff and customers alike.
This utility program manages a server install with one or many Moxie.Build services running by taking care of nightly tasks via a scheduled task.
Brief overview on the file structure and contents under Moxie. The files and folders discussed in this post are those that are essential when upgrading to the most recent version of Moxie.Build , or when troubleshooting server errors.
The Setup Table controls aspects that can be changed while the server is running, and is intended to contain both Moxie.Build specific values as well as application specific.
A single Windows OS can host many instances of Moxie.Build, these steps will guide you through the setup process.
Developing in Moxie.Build on localhost give you the advantage of working with the template files natively. When working on procedures (MOX code) you need to access that through the Procedures page in the Admin area of a Moxie.Build system, if running the server on localhost or on a remote server. When running on a remote server, you can edit the template files via the Files page in the Admin area.
Prerequisites: This page assumes that you have already set up your Moxie.Build server and logged in as an admin user. This page covers some of the basics that are involved in using the Content Management aspects of the Moxie.Build system.
The MOX coding and programming language pays heritage to BASIC, but has been crafted for the specific type of work and environment that is demanded of Moxie.Build.
Cloudflare automatically provides free client-facing certificates for your domain, even if using their free service. In addition, they provide free Origin Certificates to encrypt the connection between Cloudflare and your origin Moxie.Build server. Use this article if you are going to have Cloudflare connect to inbound open ports on your Moxie.Build server.
Prerequisites: This tutorial assumes that you have already set up your Moxie.Build server and logged in. This page covers some of the basics that are involved in managing files and folders in the Moxie.Build system.
A .mox file, with MOX code in it, can be run from the command line while a Moxie.Build system is not otherwise already running.
Moxie.Build, in short, may be used and licensed free of charge for education and non-profit organizations. Whenever it is used by government or for-profit organizations the license is granted on a subscription basis.
Moxie.Build includes a number of open source components as part of its distribution; each is subject to their own licenses as included with the files for those components.
This video demonstrates how to get started with Moxie.Build with basic customization.
In this example, we use a plain old Moxie.Build system and compare it to the MEAN Stack equivalent by building two functionally equivalent versions of a fleshed out To Do List Application. Both versions utilize local user authentication, a relational database system and the security measures found in typical production-level applications on the web today.
The following video demonstrates how to download Moxie.Build to your workstation, and run it on localhost.
Web/API Development Platform with an in-memory database, native-code CMS, and a powerful runtime environment Whether you are a new startup taking off or optimizing your business model for growth, Moxie.Build provides a robust platform with a proven track record for marketplaces, eCommerce, and business process automation
Markdown enables simple formatting of plain text via easy to remember conventions. This page will provide you with some pointers on what formatting options are available with "Moxie Flavored Markdown".
A PaaS Method may be called by any other Moxie system. In order to call a PaaS Method from MOX, the PaaS statement is used.
A Remote Method may be called by any other Moxie system. It can be used to divide up a large system among a number of backend servers, or as a public API for 3rd parties. In order to call a Remote Method from MOX, the Remote statement is used.
Has no params
A traditional way to check for hard errors and enable those errors to error softly.
Cloudflare is a first and foremost a Web Application Firewall and Content Distribution Network, among other additional services.
Takes one parameter, ServerLogText
Takes three parameters, Url, InputQuery, OutputQuery
Takes a variable number of parameters.
Takes three parameters Method, URL, Body
Has no params
Has no params
Cloudflared Tunnel exposes applications running on your local web server on any network with an internet connection with an outbound tunnel that connects directly to Cloudflare's edge network without the need to configure inbound firewall rules.
Takes one parameter, TestCondition
Takes no parameters
Takes seven parameters, TableName, OtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes seven parameters, TableName, OldFieldName, NewFieldName, Label, Note, Attr, DevNote
Takes ten parameters, TableName, OldProcName, NewProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Has no parameters
Takes six parameters, TableName, FieldName, Label, Note, Attr, DevNote
Takes nine parameters, TableName, ProcName, Type, Params, GroupTypes, Label, Note, DevNote, Source
Takes 5 parameters, Location, Mode, Class/ID, Init, bNoAutoAlign
Takes 6 parameters, Location, Mode, Div, Data, Script, Extra
Takes four parameters, FieldBase, Destination, Source, IfLenFld
Takes eight parameters, TableName, OldOtherTableName, NewOtherTableName, ParentChild, Ratio, Note, Attr, DevNote
Takes two parameters, ExcelTableData, Options
Takes two parameters, FileName, Options
Takes one parameter, a Source value
Takes one parameter, Source
Takes two parameters, Source, Value
Takes one parameter, Source
Takes two parameters, Source, Value
Takes one parameter, a Source value
Takes one parameter, Type
Takes four parameters, DestinationTable, SourceTable, bWithParents, bWithPWHashes
Takes one parameter, TableName
Takes three parameters, Location, ClassNames, AlertText
Takes seven parameters, Location, Mode, Prompt, Path, Class, Name, HelpText
Takes 6 parameters, Name, Value, Path, Domain, Expires, Other
Takes two parameters, QueryName, Title
Takes one parameter which is the keyboard key which will be used as the Access Key for a given Database Table's field.
*Note: By default, each Field's Access Key will be initialized to the first character of the Field's Label.
Prerequisites: This tutorial assumes that you have already learned about Managing Files .
Takes no parameters
Has one parameter
Has no parameters.
Prerequisites: This tutorial assumes that you have already set up a Category and Procedure if necessary. This page covers some of the basics that are involved in Front End development using the MOX language.
In order for source code to be more readily readable across teams, it is recommended that your source code always be styled according to this style guide.
ExportSchema and ImportSchema are BuiltIn procedures that are available for use with source control systems.
Takes two parameters, Text, Title
Has one parameter, a Content.Lang prefix
Takes one parameter, QueryName
Takes three parameters, Url, SaaSTenant, InputQuery, OutputQuery
Used as a scoping keyword, similar to WorkWith/End WorkWith .
Takes one parameter, the text of the exception to throw.
We empower your customers to take action.
Has no parameters
A special type of Private Method, called a Private Function, that is intended to return a single value or multiple values simultaneously.
Takes a variable number of parameters, QueryName, MethodName, [Param1, [Param2, etc...]]