If you use jwilder/nginx-proxy as your front end, you can use another image- jrcs/letsencrypt-nginx-proxy-companion-to take care of SSL certificates from Let's Encrypt. It does not do any SSL termination, so you must set up the (reverse) proxy that handles HTTPS traffic and redirects it to internal HTTP ports. Secure HTTPĬorteza server speaks only plain HTTP (and HTTP 2.0). When you spin-up an nginx-proxy container, it listens for Docker events (e.g., when a container starts or stops), reads values from the container's VIRTUAL_HOST variable, and creates an Nginx configuration that proxies requests directed to the domain configured with VIRTUAL_HOST to the container using the domain. You can find a configuration example in Corteza's docs. The easiest way to do this is with another Docker image: jwilder/nginx-proxy. We do not want to have to tell users to access Corteza on (for example) :31337 but directly on with an API served from. Unfortunately, this makes it not very user-friendly. If you want to expose them to the outside world, you need to use a different outside port. Proxy requests to containersīoth server and web-app containers listen on port 80 by default. Review the logs when starting up the services if there are any related errors. If you want to store data on your local filesystem, you might need to pay special attention to file permissions. If you use one of the simple or advanced examples, you can persist your data by uncommenting one of the volume line pairs. If you want to use Corteza in production and with other users, take a look at Corteza's simple and advanced deployment setup examples. Expose Corteza to your internal network and the world You can still access service logs with the docker-container logs command if you want. If you're not familiar with docker-compose, you can bring up the services with the -d flag and run them in the background. This test version runs on non-standard ports (:20080) and sometimes it happens that browser redirects you away from to You will notice an error "localhost refused to connect" or something similar. If this happens, just add the port number back and leave the rest of the URL. You can explore the administration area and the messaging and low-code tools with the support of the user and administrator guides. Corteza auto-promotes the first user to the administrator role. Open in your browser, and give Corteza a try.įirst, you'll see the login screen. See "Splitting services" below if you want to make it work without this purge-and-restart approach. The easiest fix is bringing all services down ( docker-compose down) and back up ( docker-compose up) again, but this will delete all data. If you misconfigure VIRTUAL_HOST, API_BASEURL, or PROVISION_SETTINGS_AUTH_FRONTEND_URL_BASE, your setup will most likely be unusable. When you see "Starting HTTP server with REST API," Corteza server is ready for use. (You can help by setting the VIRTUAL_HOST and PROVISION_SETTINGS_AUTH_FRONTEND_URL_BASE variables just right for your environment.) When Corteza server connects, it initializes "store" (for uploaded files), and the settings-discovery process will try to auto-discover as much as possible. If you change the database configuration (i.e., username, database, password), you'll get some errors. Meanwhile, Corteza server will try (and retry) to connect to the database. You'll see a stream of log lines announcing the database container initialization. Run the services by entering: docker-compose up # Map internal 80 port (where we serve the web application) Image: cortezaproject /corteza-webapp:latest # Database connection, make sure username, password, and database matches values in the db serviceĭB_DSN: corteza:oscom-tutorial (db: 3306 ) /corteza? collation=utf8mb4_general_ci PROVISION_SETTINGS_AUTH_FRONTEND_URL_BASE: http: //localhost: 20080 # use custom values for frontend URL base # this will override settings auto-discovery procedure (provision) and # Serving the app from the localhost port 20080 is not very usual setup, # Tell corteza-server where can it be reached from the outside If you change this, make sure you change API_BASEURL setting below # Map internal 80 port (where Corteza API is listening) Image: cortezaproject /corteza-server:latest
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |