Parrot Servers Infrastructure
The Parrot wiki is outdated, the blog is not properly maintained, we don’t have a federated authentication system and many services needed by our developers just don’t exist. Why? Mostly because the servers we currently have are extremely undersized for our needs, and the donations we receive are pretty far from being enough to properly sustain the new infrastructure we planned.
we already have some spare servers where to migrate (and upgrade) part of the infrastructure. Now we need to install them in a reliable datacenter, If you know someone disposed to host our servers in a proper server farm, please don’t hesitate to contact us.
This is crucial for our future.
Both the servers we already have and those we need to install (read the section above) are not enough to support the whole infrastructure, and we may need other physical and virtual servers where to host the rest of our infrastructure and make it scalable and resilient.
As said above, if you can donate servers and colocation services to the project, please contact us.
With the proper physical infrastructure, we can start deploying all the services we currently don’t have, and start making better what we already have.
We need people to help us writing a better documentation, translating it and maintaining it over time, and help us with a lot of other important tasks.
Stay tuned for new contribution opportunities.
ARM status in Parrot
Parrot for ARM has an excellent repository support, and every package in parrot is automatically built for armhf and arm64 by our official Parrot Build infrastructure.
Then what’s wrong with Parrot for ARM?
Mainly our ARM team, which was unable to build specific images for the various ARM boards.
For this reason i would like to personally take care of the entire build process of the ARM images for the various boards and not only release new updated files, but also keep them updated over time and align the ARM releases to the x86 releases.