Take a visual journey to our platform infrastructure: Presslabs Specifications
Presslabs development guidelines
This page contains information about features development, deploying, debugging, as well as recommended development life cycles.
Here you will find information regarding how you to access you site’s source code (via Gitea or git), database and media files, information about
wp-admin access and also how to grant access to collaborators.
We offer Vagrant as the default tool for local development, so in this section you have a step-by-step tutorial on how to install and configure Vagrant in order to replicate your production environment on your local computer.
We have implemented our git interface, based on Gitea, which resembles the Github development platform, but allows you to keep track of your remote repositories as well. This section presents a step-by-step tutorial on how to use our Gitea interface, based on practical examples.
We use the Presslabs-provided Git repository as the source of truth when it comes to a website’s code, and you can access your site’s source code either via git or via our Gitea interface. This makes knowing git a must-have, so to make it as easier as possible for our customers to keep track of the changes in their code, we have put together tutorials for using two git clients: GitHub Desktop and Fork.
These two clients work for both Windows and macOS:
We also have tutorials for using git command lines:
To clone your code locally, you can use either the HTTPS protocol, or the SSH protocol. The latter implies setting up your public key in our dashboard. In this section are described the steps you need to follwo in order to generate a SSH key pair, as well as how to configure your public key on all the operating systems.