curl -Lso bitwarden.sh https://go.btwrdn.co/bw-sh \
&& chmod +x bitwarden.sh
Adjust additional configuration settings in ./bwdata/env/global.override.env and restart.
If you need to make additional configuration changes, you can modify
the settings in `./bwdata/config.yml` and then run:
`./bitwarden.sh rebuild` or `./bitwarden.sh update`
Next steps, run:
For some reason to install Ajenti on Ubuntu 18.04 is tricky. So I have the steps here which are needed to make this so. Most of the insturctions say to install python-imaging_4.1 but this no longer exists.
As Daniels prophecy there would be the two kings pushing each other. Looking forward to the future events.
40 “In the time of the end the king of the south will engage with him in a pushing,* and against him the king of the north will storm with chariots and horsemen and many ships; and he will enter into the lands and sweep through like a flood.
A few weeks ago at work, I was tasked with the project of decommissioning one of our older Windows Server 2008 machines and upgrading it to Windows 2012. I was initially a little worried, seeing as this server ran a lot of key roles, such as DHCP, DNS, was a Domain Controller, and also acted as a print server as well as a few other services. As I was migrating the DHCP role, I wondered if there was a simple way of exporting all of the settings, such as DHCP scope and reserved IP addresses. Turns out there was, and it went off without a hitch!
Here’s how I did it:
Log on to the old/existing DHCP server.
Open a command prompt as Administrator.
On the Action menu (from within the DHCP management console), click “Backup”.
Type netsh dhcp server export C:\Users\\Desktop\dhcp.txt all, and then press ENTER.
Install the DHCP role on the new (2012/2016) DHCP server using Server Manager.
Copy the exported DHCP text file to the desktop of the new DHCP server.
Verify that the DHCP service is installed and started on the new DHCP server.
Open a command prompt as Administrator (on the new server)
Type netsh dhcp server import C:\Users\\Desktop\dhcp.txt all, and then press ENTER
Open DHCP management console on the new server.
In the console tree, right-click DHCP.
If your old DHCP server is in the same network/subnet as the new DHCP server, you’ll notice that the old DHCP server has been de-authorized automatically. This is to prevent two DHCP servers from handing out conflicting addresses.
Check to make sure that your new DHCP has all of the same settings, options, scopes, and reservations set as the current one. If done correctly, everything should have been brought over. I was pretty impressed as to how well this worked and just how seamless it truly was.
ssh -L 9000:localhost:5432 firstname.lastname@example.org
ssh -L 9000:imgur.com:80 email@example.com
ssh -L 8000:10.0.0.30:8000 firstname.lastname@example.org
For example with gekko you can use
ssh -L 3000:127.0.0.1:3000 email@example.com
Works better then the reverse proxy.