*require* the web ui as "the one and only"
Reported by ronin-278 (at lighthouseapp) | July 25th, 2008 @ 10:38 AM | in 0.1
Meaning: what would be a real use case of another UI that wouldn't be web-accessed?
I doubt anyone will fancy ssh-ing to a server to run a command that tells you what happened with the latest build. At least when you can hit a website with pretty much the same speed.
And besides, making it optional forces us to have a second web app for github. That means you need double the config and resources -- as in, another subdomain/port to run it? simplicity FAIL in our part.
So, let's make the web ui "required" (not that we need to change much for that) and change the github post to post /14308/push
Thoughts?
Comments and changes to this ticket
-
ronin-278 (at lighthouseapp) July 26th, 2008 @ 03:12 AM
- State changed from “new” to “resolved”
(from [12826e26065e9e2f2348ae52eb538d23a4aa1d28]) Move GitHub's post-receive script to the web UI [#19 state:resolved]
-
ronin-278 (at lighthouseapp) July 26th, 2008 @ 03:12 AM
(from [d775d16e93c36f8dbed3acee7fd4435adeeee29f]) Move the web ui down a level in the directories, first step to make it the 'required' UI [#19]
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Automated continuous integration server that doesn't suck.
Simon Rozet