Also won't let me push, because something thinks it's a non-fast-forward (it is, unless I'm drunk):

$ git push phorge 2abd75c162:master
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 817 bytes | 408.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: +---------------------------------------------------------------+
remote: |      * * * PUSH REJECTED BY EVIL DRAGON BUREAUCRATS * * *     |
remote: +---------------------------------------------------------------+
remote:              \
remote:               \                    ^    /^
remote:                \                  / \  // \
remote:                 \   |\___/|      /   \//  .\
remote:                  \  /V  V  \__  /    //  | \ \           *----*
remote:                    /     /  \/_/    //   |  \  \          \   |
remote:                    @___@`    \/_   //    |   \   \         \/\ \
remote:                   0/0/|       \/_ //     |    \    \         \  \
remote:               0/0/0/0/|        \///      |     \     \       |  |
remote:            0/0/0/0/0/_|_ /   (  //       |      \     _\     |  /
remote:         0/0/0/0/0/0/`/,_ _ _/  ) ; -.    |    _ _\.-~       /   /
remote:                     ,-}        _      *-.|.-~-.           .~    ~
remote:   *     \__/         `/\      /                 ~-. _ .-~      /
remote:    \____(Oo)            *.   }            {                   /
remote:    (    (..)           .----~-.\        \-`                 .~
remote:    //___\\  \ DENIED!  ///.----..<        \             _ -~
remote:   //     \\                ///-._ _ _ _ _ _ _{^ - - - - ~
remote:
remote:
remote: DANGEROUS CHANGE: The change you're attempting to push updates the branch 'master' from '51cb7a3db9e8' to '2abd75c16237', but this is not a fast-forward. Pushes which rewrite published branch history are dangerous.
remote: Dangerous change protection is enabled for this repository.
remote: Edit the repository configuration before making dangerous changes.
remote:
[2021-06-17 15:41:20] EXCEPTION: (Exception) Unable to write to logfile "/var/log/phorge/ssh.log"! at [<arcanist>/src/filesystem/PhutilDeferredLog.php:193]
arcanist(head=master, ref.master=246e604a070f), phabricator(head=master, ref.master=5e3f4e418f5c)
  #0 <#2> PhutilDeferredLog::__destruct()
  #1 phlog(Exception) called at [<arcanist>/src/filesystem/PhutilDeferredLog.php:201]
  #2 PhutilDeferredLog::write() called at [<arcanist>/src/filesystem/PhutilDeferredLog.php:155]
  #3 PhutilDeferredLog::__destruct()
[2021-06-17 15:41:20] EXCEPTION: (Exception) Unable to write to logfile "/var/log/phorge/ssh.log"! at [<arcanist>/src/filesystem/PhutilDeferredLog.php:193]
To ssh://secure.phorge.it:2222/source/phorge.git
 ! [remote rejected]       2abd75c162 -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://secure.phorge.it:2222/source/phorge.git'

There's some issue with the SSH settings here - probably file permissions?

Do we want to make this an application or an extension? I'd lean toward the latter, it might be a good one to seed our new extension library with...

Sorry about the spam... I've gone ahead and made all the component projects of Phorge public. Is there anything else we need to do here?

In general, the Welcome message stuff (And most of the concerns I outlined in T15003#216) will be taken care of in a new root / webpage(s) that will live at phorge.it and/or www.phorge.it - See T15000#234 for some background discussion

Just to keep this here for posterity

Looks like we.phorge.it is the winner coming out of that, with a static site hosted at the apex

In T15000#231, @Ekubischta wrote:

my vote would be phorge.it - simpler, easier to market, easier to say and easier to link to. - You could auto-redirect various common www., secure. etc.

my vote would be phorge.it - simpler, easier to market, easier to say and easier to link to. - You could auto-redirect various common www., secure. etc.

+1 for demo instance! - Phorge Playground or something like that

I like the demo instance idea...

Another idea here: Why don't we create a demo instance with all of the defaults? Like, half a dozen sample tasks, some sample repositories, allow users to mess around with it, and wipe it every hour back to a default database. I've seen that in multiple open source projects.

Reopening, we're not done yet.

• move hostname to https://phorge.it

Or did we decide against it? Do we want to keep it secure.?

In T15000#219, @chris wrote:

Fixed for real this time. I had an error in the sudoers file. Thought the webserver was running under a different user. But just cloned rARC with its HTTPS URI successfully, so should be hunky dory now hopefully.

Fixed for real this time. I had an error in the sudoers file. Thought the webserver was running under a different user. But just cloned rARC with its HTTPS URI successfully, so should be hunky dory now hopefully.

The logged out dashboard is already different from the logged-in default dashboard:

In T15000#211, @chris wrote:

Good catch, thanks!

no problem! Trying to put together a Docker/devcontainer based dev environment to make it easy for potential contributors.

Edit: resolved

So - If I am a brand new user that comes across this main Phorge page

No need to apologize, i wasn't super clear myself, so let me try to make my point in a more cogent manner. The main thing that bothered me with what happen is that our default should be to use the phorge's default (that I happen to find good myself, but it is not super relevant to the point). This comes down to dogfooding. The default configuration is what we are going to put into people's hand. We must ensure this is as good as possible for as many users as possible right out of the bat. This will never happen if the standard phorge install doesn't use the default, because what's out of sight also typically is out of mind.

Good catch, thanks!

In T15007#209, @avivey wrote:

err, why do we need Spaces?

err, why do we need Spaces?

• Configure Diffusion

S1 has been adjusted (the option didn't exist until the switch you flipped was active). I've also adjusted all tasks (per-object policies) and the dashboard panels. I will make a pass at the subprojects unless you want to go for it.

Okay, I added one module (which was the "Welcome" box) and moved three modules into a tabbed view ("recent stuff"). While I did remove some features from the sidebar, those are editable at https://secure.phorge.it/home/menu/configure/custom/ . This task was up for 24 hours for feedback, and was mentioned on Zulip during that time.

Also, S1 isn't public, contrary to what the name says, so this effectively just changes the error message at the moment.

In T15007#191, @deadalnix wrote:

In T15007#182, @Matthew wrote:

We are holding off, until other tasks in T15000 are complete.

It's on a subdomain that isn't listed anywhere and registration require approval, so that shouldn't be a problem.

This nevertheless regressed the dashboard for everybody vs what was before. I'm sorry but I don't want to be welcome to create my own dashboard with the information I see fit on it, because I had one that was pretty good to begin with. You just broke everybody's dashboard. If it is for logged out users, and you don't want to put it up now, then just park it somewhere.

In T15007#182, @Matthew wrote:

We are holding off, until other tasks in T15000 are complete.

Changes:

• differential: default view policy: public
• diffusion: default view policy: public and default push policy; blessed committers
• maniphest: default view policy: public and default edit policy: task author or trusted contributors.
• project: default view policy: public
• paste: default view policy; public
• countdown: default view policy; public

So I edited policy.allow-public and set it to true in the DB.

When changes are made please document what all they end up being.

We are holding off, until other tasks in T15000 are complete.

This dashboard was originally intended for non-logged in users. See discussion in T15000. We are holding off opening this install until anti-spam measures are configured. Logged-in users are welcome to create their own dashboards, with information they see fit.

I'm going to have to be honest here. While this is more appropriate for logged out users, this is a net regression for a regular user.

Projects created, sorry about the spam.