PHABRICATOR on NS

Feature
162

and this /var/lib/nethserver/vhost/phab/phabricator/bin/config set pygments.enabled true
will be executed as?

163

The command is: config set pygments.enabled true

Now you use the template and replace <YOUR COMMAND HERE> with the command.

/bin/bash -c "source /opt/rh/rh-php72/enable; cd /var/lib/nethserver/vhost/dev/phabricator/bin; php -dmemory_limit=512M <YOUR COMMAND HERE>"

Then you get:

/bin/bash -c "source /opt/rh/rh-php72/enable; cd /var/lib/nethserver/vhost/dev/phabricator/bin; php -dmemory_limit=512M config set pygments.enabled true"

164

i guess this does it:

/var/lib/nethserver/vhost/dev/phabricator/bin; config set pygments.enabled true

1 Like
165

and these two would be:

bin/config set environment.append-paths --stdin < path.json
bin/config set diffusion.ssh-port 2222

funny i try to adapt the same way but does not work.

166

Please post errors if somethings not working.

I think you missed the correct path to the path.json file, I created it in ~, it depends on your installation:

/bin/bash -c "source /opt/rh/rh-php72/enable; cd /var/lib/nethserver/vhost/dev/phabricator/bin; php -dmemory_limit=512M config set environment.append-paths --stdin < ~/path.json"

This just works without problems:

/bin/bash -c "source /opt/rh/rh-php72/enable; cd /var/lib/nethserver/vhost/dev/phabricator/bin; php -dmemory_limit=512M config set diffusion.ssh-port 2222"

167

bin/config set cluster.mailers ā€“stdin < mailers.json

168

Whatā€™s wrong? Is there an error?

It should work similar as described in my previous post.

169

yes there is
but i think its something to do with these:

[
  {
    "key": "mailer",
    "type": "smtp",
    "host": "mailservername",
    "port": "port #",
    "username": "user_name",
    "password": "user_password",
    "protocol": "ssl/tls"
  }
]
170

trying to implement notifications, as shown here:
https://secure.phabricator.com/book/phabricator/article/notifications/

nw i have a headache

1 Like
171

i added an alternate file domain as seen here: https://secure.phabricator.com/book/phabricator/article/configuring_file_domain/

but now i am getting an error on the server.
i guess the main reason is because i have not defined that the domain should point to phabricator. how can i do that. @mrmarkuz @danb35

172

Iā€™m sorry, Iā€™m not a mind-reader, so I canā€™t help you.

1 Like
173

will update with something more meaningful.
for the notification server, as well as implementing a secondary files domain.

174

How can i implement another domain to be able to reach the Phabricator instance that i have installed.

i managed to setup files storage to s3. and when i try to implement the files domain, the entire software breaksdown.
I have already created a separate subdomain, pointed it to the neth instance, an already installed SSl to it.

175

I am currently having challenges pushing to the repo with ssh, while also getting error 500 with https.

i followed these instructions as on the document

### Users/Permissions for code checkout and update

In order for users to be able to check out code and commit changes, there's quite a bit of configuration that needs to be done. The relevant users were created above, but the system needs to be set up to allow them to perform the relevant updates. These instructions will set up your system to support these operations via HTTP (if supported by your version control system of choice) and SSH. As part of the process, this will create a second sshd service running on port 2222. If your main SSH service is running on port 2222, you'll need to choose a different port below. From the CLI, run:
176

Please check logs (phd.log?, /var/log/messages) for more error details.

I found there are some troubleshooting steps as regards ssh/https:

ā—‰ Diffusion User Guide: Repository Hosting (search for troubleshooting)

https://secure.phabricator.com/book/phabricator/article/troubleshooting_https/

Sorry, I couldnā€™t find the instructions/document.

177

Sad news, to whom may concern.
Phabricator is no more.
https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/
Currently, i have no idea why.

178

Hey I was aware of this news for a while now since June.
The project has been phorked and is now phorge
Available at https://we.phorge.it/

Been following what they are doing on the project, once they get a few things Iā€™ll be looking to try a new installation tutorial.

I can see youā€™ve been looking for project management solutions

179

Taking myā€¦ experiences. Headaches. Keyboard throwing into the garden when Iā€™m not good enough to making things work.
Anyway: hoping to find soon a ā€œstableā€ of Phorge, and maybe a NethServer 8 Module/container for that.

180

Yes, definitely Iā€™ll just do an installation instruction, if I would have Lear t how to build modules, I can attempt to build one.

The phorge team are working on getting rebranding right in the software. Most elements were previously hard coded but are now working getting them easy to implement.

They are also modularising the system so it plays well with other systems.
Overall its a fantastic system, am glad alot of people have joined ha ds to maintain it. Even original developers are supporting the process.

Wikimedia is a huge user and are also actively supporting.
The power of opensource is that a great project with many users will never die.
Atleast it uses php, so many devs available

181

This is quite a good gamechangerā€¦

Opensource is not about money, but without money (earned, donated, saved) wonā€™t be possible, at least for mantaining and evolving project.

Wikimedia is a lot interesting player, but still not ā€œthat moneyā€ that could boost the project. So it will take IMVHO a considerable amount of time to have a working fork. Thenā€¦ it will be necessary

  • maintenance
  • bugfix
  • development