Nasqueron Operations SIG maintains devservers. They offer a remote development environment for Nasqueron and open source projects.
What server to use?
- WindRiver, for any general-purpose task
- Ysul, for webserver-legacy sites
- Dwellers, for Docker development
- Eglide, if you need an IRC session
How to get access?
You can ask it on DevCentral.
To speed up the process, you can follow NOG instructions at Operations grimoire/Create and revoke user accounts on Salt servers and send a commit to Differential against our operations repository.
|Ysul / WindRiver||nasquenautes||for general purpose development|
|Dwellers||dev-docker||for Docker development (group still to create)|
|Eglide||shell||for IRC purpose|
Normally, devservers run under FreeBSD. That means your userland is a BSD one, and some commands arguments can be different if you're used to Linux. GNU coretools utilities are installed and prefixed by the letter g, e.g. gmake or gsed.
The most useful GNU commands are:
* gmake when the Makefile has been written for GNU make * gsed -i to perform inline replacements * gwatch (/usr/sbin/watch allows the user to examine all data coming through a specified tty, that's quite different)
Note grep is the BSD one, but documented to be GNU compatible.
- Use your /home/luser directory for anything personal
- Use /srv or /var when you need to share something, that generally requires a Salt config to give shared rights to that directory
- /var/51-wwwroot on Ysul is to use instead of your home folder for staging area of web applications you want to serve
Works on server with the devserver-mysql role.
You've access to test_% databases, so you can without any specific configuration use that for unit tests. It's even OK to connect without login or password for the test_% namespace.
If you need any other database and app config, you can request it on DevCentral.
For long term projects, you can also specify where you want the credentials to be be provisioned, or request a Vault AppRole for your application to fetch them securely.
If you wish to have control of what stable and nightly Rust versions to use, you can use Rustup.
To use it, the command
rustup-init is available as an alternative to the curl magic documented on the Rustup web site (actually it's a fairly recent version of that script saved locally).
If you're OK with the Rust version installed by OS packages, feel free to call directly cargo or rustc.
You can generate project documentation with the `cargo doc` command.
The following software are maintained as phar or repository clones in /opt:
- psysh, REPL shell to test PHP code (with PHP documentation available at /usr/local/share/psysh/php_manual.sqlite)
- psalm, for static analysis
- doctum and phpdoc (phpDocumentor) to generate documentation
Most of those tools have wrappers in /usr/local/bin trying to detect if a version is installed locally for the PHP project through Composer and switching to that version if available.
So by running "phpunit", you'll run your Composer version and the system version when missing.
To generate documentation for your code,
doctum commands are available, including GraphViz and PlantUML for phpDocumentor classes graphes.