It seems that, for the aforementioned distribution/version/architecture combination Gogs would always fail to start due to the lack of a 64-bit libpam.so.0 package.

A simple solution is to switch to an i386 gogs package, and setting the default in such a way will probably be better in Ubuntu's case (although no idea about 16.04 LTS at the moment).

See: gogs/gogs#145 (comment)

Change security -> INSTALL_LOCK to true in custom/conf/app.ini will omit install page step.

Need to use defaults instead of vars to allow overriding.

Currently, the startup script seems to be merely unpacked from the Gogs distribution and symlinked to init.d. This makes the various role customization vars (most notably the user setting) worse then useless, since the service will be inconsistently configured and unable to start.

To reproduce, simply alter gogs_user or gogs_user_home in the role configuration and run the role on a fresh setup.

The init script included with Gogs seems to not want to work with RHEL/CentOS 7. See: https://travis-ci.org/geerlingguy/ansible-role-gogs/jobs/109519333#L858

TASK: [role_under_test | Ensure Gogs is running.] ***************************** 
failed: [localhost] => {"failed": true}
msg: Failed to start gogs.service: Unit gogs.service failed to load: No such file or directory.

I even tried explicitly restarting the systemctl daemon but that didn't seem to help (I had the following code inside init-setup.yml):

# SEE: https://github.com/ansible/ansible-modules-core/issues/191
- name: Restart systemctl daemon on systemd systems.
  shell: systemctl daemon-reload
  when: gogs_file_symlinks.changed and (ansible_os_family == "RedHat" and ansible_distribution_major_version|int == 7)

Use option: var syntax where needed, clean things up, etc.

MacOS 10.11
docker-machine version 0.12.2, build 9371605 (via brew)
docker version 17.07.0-ce, build 8784753 (via brew)

When I run the tests, I get this error when it tries to enable and run the service.

TASK [role_under_test : Ensure Gogs is running.] *******************************
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/bin/systemctl", "failed": true, "msg": "Failed to get D-Bus connection: Unknown error -1", "rc": 1, "stderr": "Failed to get D-Bus connection: Unknown error -1\n", "stderr_lines": ["Failed to get D-Bus connection: Unknown error -1"], "stdout": "", "stdout_lines": []}

I haven't been able to find anything online regarding this, but it seems to be an issue with docker on MacOS, as the tests with Travis are obviously passing.

@geerlingguy or anyone else, any idea how to fix this?

I set it to a different port but it still attempts to run on 3000. I searched the repo for gogs_http_port for how it is used and only two instances show up: in the README and the default setting. Is this setting used at all?

Hi, first thanks for the great work!

I'm creating this "issue" because I saw you have this

templates/gogs.unit.j2:#After=mysqld.service

but it doesn't uncomment when gogs_use_mysql: true...

How can I do that? This is making gogs not come back when the box is rebooted.

Thanks,
Felipe

See related: ansible/ansible-modules-core#915

Build failure: https://travis-ci.org/geerlingguy/ansible-role-gogs/jobs/178326322

TASK [role_under_test : Ensure Gogs is running.] *******************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service \"'gogs'\": "}

We're currently relying on the init scripts here: https://github.com/gogits/gogs/tree/master/scripts/init

But for systemd systems, we should use the unit file (like https://github.com/gogits/gogs/blob/master/scripts/systemd/gogs.service). To make it work on all systems correctly, we'll have to template our own copy.