Explore >> Select a destination
|
You are here 
|
blog.jak-linux.org | ||
| | | | |
blog.cy.md
|
|
| | | | | ||
| | | | |
peter.eisentraut.org
|
|
| | | | | When the PostgreSQL project makes a release, the primary artifact of that is the publication of a source code tarball. That represents the output of all the work that went into the creation of the PostgreSQL software up to the point of the release. The source tarball is then used downstream by packagers to make binary packages (or file system images or installation scripts or similar things), or by some to build the software from source by hand. | |
| | | | |
www.morling.dev
|
|
| | | | | As a software engineer, I like to automate tedious tasks as much as possible. The deployment of this website is no exception: it is built using the Hugo static site generator and hosted on GitHub Pages; so wouldn't it be nice if the rendered website would automatically be published whenever an update is pushed to its source code repository? | |
| | | | |
group.miletic.net
|
|
| | | Group for Apps and Services on Exascale Research Infrastructure is a research, development, and teaching unit at FIDIT + MedRi. | ||
