Instantly generate production-ready .NET and Node.js backend apps 🚀

Introduction

Amplication is a robust, open-source development platform crafted to revolutionize the creation of scalable and secure .NET and Node.js applications. We eliminate repetitive coding tasks and deliver production-ready infrastructure code, meticulously tailored to your specifications and adhering to industry best practices.

Our user-friendly interface fosters seamless integration of APIs, data models, databases, authentication, and authorization. Built on a flexible, plugin-based architecture, Amplication allows effortless customization of the code and offers a diverse range of integrations.

With a strong focus on collaboration, Amplication streamlines team-oriented development, making it an ideal choice for groups of all sizes, from startups to large enterprises. Our platform enables you to concentrate on your business logic, while we handle the heavy lifting.

Experience the fastest way to develop .NET and Node.js applications with Amplication.

Getting Started

First of all, it should be mentioned that there two possible modes: production and development.

Production Mode

In order to run the server for production mode these commands have to be executed:

npm run build
npm run start

After the first command all the static pages will be save as json and html files as cache files. The second command starts the server, which is usually http://localhost:3001

Development Mode

For starting the development server:

npm run dev

Open http://localhost:3000 with your browser to see the result. You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

The API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js. The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Note : there is no Next.js cache functionality for development mode.

Deployment

Both the Amplication website, blog server and blog admin-ui, are hosted on the staging cluster aswell as the production cluster. The repository follows a similar approach to the main amplication repository, where the staging environment will be deployed by commits to master and the a release - i.e., a tag of a specific commit on master - will deploy to the production environment.