amplication / amplication-site Goto Github PK

View Code? Open in Web Editor NEW

13.0 3.0 23.0 44.91 MB

Amplication's website!

Home Page: https://amplication.com/

JavaScript 66.42% CSS 33.34% Dockerfile 0.16% SCSS 0.07%

hacktoberfest nextjs react

amplication-site's Introduction

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.

amplication-site's People

Contributors

Stargazers

Watchers

amplication-site's Issues

Add routs to Web App

We need to support redirects on

blog.amplication.com
staging-blog.amplication.com

We are migrating the amplication domain to that site so it needs to support as well
amplication.com

HTTP should redirect to HTTPS

create a load balancer with terraform and point to the blog client cloud run with specific special routes

Redirects:
/jobs -> https://amplication.breezy.hr/
/discord -> https://discord.gg/KSJCZ24vj2

Add missing `privacy-policy`

In the bottom of the site landing page, we have a privacy policy link.

when trying to access https://amplication.com/privacy-policy we receive 404 error (page not found).

please import the privacy policy from the old site (amplication/site repository)

Need to refactor redirect paths for /docs.

For now, the redirect from blog.amplication.com/docs/[ANY-PATH] ---> docs.amplication.com/docs/[ANY-PATH] works.

This is a workaround I've made and needs to be done better.
the redirect works by a written list on main.tf which holds all the paths for 'docs'.
It means that if we want to add more paths in the future we need to update the list with the additional paths for '/docs/[ADDITIONAL-PATH]', and update the terraform.

First, I tried to work with wildcards but without success:
path_rule: "/docs/"
Host_redirect: docs.amplication.com
Path_redirect: "/docs/"

the results in browser: blog.amplication.com/docs/deploy ---> docs.amplication.com/docs/* (page not found)

Improve Cloud Run responsiveness

Change the cloud run deployment to be more responsive.
set the production cloud run:

CPU to 4
memory to 512
min instances to 1
min instances to 5
set the concurrency to 1000
set allocate always-on CPU

Update load-balancer

Add redirects

HTTTP -> HTTPS
amplication.com/docs -> docs.amplication.com

Migrate CI\CD from blog repository

in amplication/blog we have:

Dockerfile for creating site image
Terraform for the site hosting on GCP
Github actions for CI\CD

migrate all to this repository

https://amplication.com/docs/getting-started	https://docs.amplication.com/docs/getting-started/
https://amplication.com/docs/sync-with-github	https://docs.amplication.com/docs/sync-with-github/
https://amplication.com/docs/deploy	https://docs.amplication.com/docs/deploy/
https://amplication.com/docs/cli	https://docs.amplication.com/docs/cli/

make a rule that will redirect all https://amplication.com/docs to https://docs.amplication.com/docs