release-critical parts of community infrastructure

[markus2330]

Thanks to @BernhardDenner we quickly recovered from the breach at libelektra.org. Unfortunately, some release-critical parts are not yet fixed:

• git repos for ftp+docu: Before the breach it was possible to directly push the release tarballs and docu to the server. It seems these parts are now plain files and not git repos anymore?
• stretch debian packages not provided: the stretch build job happily builds debian packages but currently there is no way to download them (No webserver reachable at https://unstable.libelektra.org/elektra-stable/).

And small new wishes for the release notes:

• book.libelektra.org to redirect to https://github.com/ElektraInitiative/book
• pulls.libelektra.org to redirect to "Pull requests" (https://github.com/ElektraInitiative/libelektra/pulls/)
• puppet.libelektra.org to redirect to https://github.com/ElektraInitiative/puppet-libelektra

And:

• fix feed URL Fix feed url #1684

[BernhardDenner]

@git for docu: I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol. Maybe it was configured somewhere else I not aware of.

Should this be usable by other users too, e.g. pulling from anonymous? If not, I prefer to use SSH for the transport layer, as this supports key based authentication and works out of the box by just creating a local user.

[markus2330]

@BernhardDenner Thank you for looking into it!

I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol.

It was done using ssh but the repos were configured in a way that they automatically check out when something is pushed into them.

as this supports key based authentication and works out of the box by just creating a local user.

Yes, I would also prefer that. Can you create a user with correct permissions and add my public key?

[BernhardDenner]

Git repo for releases/downloads now up2date again. See mail for instructions.

[BernhardDenner]

New subdomain redirects added, Letsencrypt setup will be done in right now.
However, you still have to update the liblektra.org domain, because these subdomains are not registered right now

[BernhardDenner]

SSL certificate is now updated too, thus includes the now subdomains.

[markus2330]

Thank you! Subdomains are added.

(I also wrote you an email.)

[markus2330]

Stretch repos are the only missing item. The git repos for ftp/doc work wonderful!

[markus2330]

Automatic checkout of doc does not seem to work. Is it a problem if non-git files are lying around? (They are periodically copied from the build server).

[markus2330]

@BernhardDenner Any update here?

[markus2330]

Seems like we have an additional problem: The mailman Web interface is broken: I cannot subscribe/unsubscribe (seems to do a redirect to http when submitting form data)

[markus2330]

It would be great to have this running for 0.8.23. @ingwinlu what is the current status?

[ingwinlu]

I tried to get it to build debian packages in docker containers but did not get very far, mostly because I needed to revamp the current images (we need huge images to build all the debian packages because of all the dependencies).

Additionally the feedback on #1866 kept me busy and all the other 'urgent' stuff that I am assigned to.

[markus2330]

Which 'urgent' tasks did I assign?

• I do not know if Prepare Jenkinsfile #1866 is urgent, I thought it would be good to have it within the release notes.
• create live demo of web-ui #1901 seems unrealistic for this release anyway.
• The Debian packages are basically the only thing that are needed by external people.

I renamed 'bounty' to 'urgent' to make more clear which the urgent tasks are.

[ingwinlu]

#1866 in itself might not be urgent. but whenever I need to add something like the homepage build or the debian packaging I have to test it locally. And this takes forever as my pc takes 15min+ to build elektra.

Having it merged would mean I could open new PR's for both of those tasks where we could discuss the problems that occur during them as well as have the ci system display the logs in an easily acceptable manner. This would make my life considerable easier.

[markus2330]

Yes, I am for merging it soon, too.

From my point of view only docu is misssing.

[markus2330]

Closing, because it is a duplicate from #1752. Other issue was migrated.