currently set up manually, Aptly on Darwini should be set up by code for repeatability and verification
@ kde:sysadmin/neon-server-deploy
currently set up manually, Aptly on Darwini should be set up by code for repeatability and verification
@ kde:sysadmin/neon-server-deploy
Probably it should just use the nightly packages, I can't remember if there's a reason why not
deb http://repo.aptly.info/ nightly main
Because it's not system-wide and there is no reason for it to be.
systemd rigging would need iac eitherway.
Devops clouded ansible orchestration method
https://github.com/jriddell/kdeneon-server-deploy
move to kde.
I am also not entirely sure why we need ansible here. but ok
needs a readme. doesn't work for me
fails to provision from scratch
$ ./deploy 192.168.1.19 | FAILED! => { "changed": false, "failed": true, "msg": "file (.config/systemd/user/aptly.service) is absent, cannot continue", "path": ".config/systemd/user/aptly.service", "state": "absent" } 192.168.1.19 | FAILED! => { "changed": false, "failed": true, "msg": "file (bin/) is absent, cannot continue", "path": "bin/", "state": "absent" } 192.168.1.19 | SUCCESS | rc=0 >> 192.168.1.19 | FAILED | rc=5 >> Failed to start aptly.service: Unit aptly.service not found. 192.168.1.19 | FAILED | rc=1 >> Can't connect to localhost:9090 Connection refused at /usr/share/perl5/LWP/Protocol/http.pm line 47.
fixed return values
I don't know if scratch is going away, last I heard Ben was still working out how to integrate it/implement it in phabricator
makes directories now
you got rid of getting latest nightly aptly?
Yes. I take offense with you installing aptly on my system, without adding the gpg key, without removing it again, just so you get out of reading the aptly readme and doing a proper build.
Still not passing with new files. Also still ignores failures (return values)
darwini.kde.org | FAILED! => { "changed": false, "failed": true, "msg": "file (.config/systemd/user/aptly.socket) is absent, cannot continue", "path": ".config/systemd/user/aptly.socket", "state": "absent" } darwini.kde.org | FAILED! => { "changed": false, "failed": true, "msg": "file (.config/systemd/user/proxy-to-aptly.service) is absent, cannot continue", "path": ".config/systemd/user/proxy-to-aptly.service", "state": "absent" } darwini.kde.org | FAILED! => { "changed": false, "failed": true, "msg": "file (.config/systemd/user/proxy-to-aptly.socket) is absent, cannot continue", "path": ".config/systemd/user/proxy-to-aptly.socket", "state": "absent" }