![]() ReCAPTCHA: Certain actions, such as when email is sent, require a CAPTCHA to prevent abuse. Mailgun has a free tier that should cover most experimental and low-traffic usage. Email SaaS: If you want Octave Online Server to be able to send transactional emails, such as for email-based login, you need a Mailgun or Postmark account. Keep in mind that MongoDB will contain personally identifiable information for user accounts. My experience is that it takes some time to correctly configure a fast and secure MongoDB installation. Unlike Redis, MongoDB is not as central of a piece in the infrastructure, so it is possible to use a remotely hosted MongoDB if you do not want to host it locally. MongoDB: Install and run a MongoDB instance. ![]() Also see back-filesystem/README.md for instructions on how to configure a Git file server for Octave Online Server. For more information, see Git on the Server. It boils down to a server, which could be the current server, with a low-privileged user usually named "git". Git Server: In order to persist user files between sessions, you need to set up a Git file server. This is the default version on CentOS 8.Īlthough it is possible to use a third-party hosted Redis instance, this is not recommended because Redis latency is amplified due to its central role in the Octave Online Server architecture. Node.js: Octave Online Server is built and tested with Node.js LTS version 10. Most of Octave Online Server should work on macOS, but this has not been tested. It is recommended that you use CentOS 8, although other modern distributions should work also. Operating System: Octave Online Server is built and tested exclusively on GNU/Linux. utils-auth/README.md for an optional standalone user authentication serviceĮvery subdirectory of the top-level Octave Online Server directory has a README file that explains what the contents of the directory is for.utils-admin/README.md for an optional admin panel.shared/README.md for code shared by multiple components.entrypoint/README.md for helper scripts to run Octave Online Server.back-octave/README.md for GNU Octave bindings for the back server.back-filesystem/README.md for filesystem I/O on the back server.There are also a few more directories for other components: It is recommended that you feel comfortable with basic system administration before attempting an installation.įor more details on operating each of the three components, see the respective README files: ![]() Note: Octave Online Server has a lot of moving parts. This is the fastest way to get off the ground. Read containers/README.md for details on running a containerized version of all of Octave Online Server for use with trusted users. The Client uses ES5 the Front Server uses TypeScript and the Back Server uses ES6. Languages: All code is written with JavaScript technologies, although for historical reasons, the three components use different flavors of JavaScript. It is also possible to run both the Front Server and the Back Server on the same computer. Scaling: Front Servers and Back Servers can be scaled independently (in general, you need more Back Servers than Front Servers). User files are stored in Git on the Server and are accessed primarily from the Back Server. User account information is stored in MongoDB and is accessed primarily from the Front Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |