If you have an existing version of Allsky, stop it:

sudo systemctl stop allsky
cd

1. To upgrade the old version and keep its settings:

   mv  allsky  allsky-OLD

2. To save the old version but not use it:
   

   mv  allsky  allsky-SAVED

   At some point you'll want to delete the SAVED version so it doesn't use disk space.
3. To delete the old version - only select this option if you're sure you don't want any saved images, darks, and configuration settings:

   rm  -fr  allsky

Continue to the Pre installation section.

The following needs to be done once prior to installing Allsky:

1. If this is a new Pi, you'll need to install the Raspberry Pi Operating System (OS) on it. We recommend installing the Desktop version of Pi OS.
2. Make sure your Pi has a working Internet connection. If you have a choice between a wired LAN and wireless WLAN connection, choose the wired connect - they are faster and more reliable. If you use Power over Ethernet (PoE), you can run a single ethernet cable to your Pi.
3. Ensure git is installed:

   sudo apt-get install git

The following commands put the new release of Allsky in ~/allsky. Except for some system files, all Allsky-related files reside in this directory.

cd
git clone  --depth=1  --recursive  https://github.com/AllskyTeam/allsky.git
cd allsky
./install.sh

The git clone command will take a couple minutes and should produce output similar to what's below. The new allsky directory is approximately 75 MB after download.

Cloning into 'allsky'...
remote: Enumerating objects: 16464, done.
...  more commands here
Receiving objects: 100% (16464/16464), 94.03 MiB | 1.13 MiB/s, done.
Resolving deltas: 100% (9845/9845), done.
Submodule 'src/sunwait-src' (https://github.com/risacher/sunwait) registered for ...
Cloning into '/home/pi/allsky/src/sunwait-src'...
remote: Enumerating objects: 130, done.
...  more commands here
Resolving deltas: 100% (72/72), done.
Submodule path 'src/sunwait-src': checked out '102cb417ecbb7a3757ba9ee4b94d6db3225124c4'

The Allsky installation prompts for several items including:

• New host name, if not the default of allsky. If you have more than one Pi on the same network they must all have unique names. For example, if you have a test Pi you may want to call it allsky-test.
• Locale to use. This determines what the decimal separator is in log output (period or comma).
  Note that the default locale is en_GB.UTF-8 where the Pi is developed.
• Adding swap space if needed. Swap space effectively increases the amount of memory your Pi has. Insufficient swap space is one of the leading causes of timelapse video creations problems.
• Putting the ~/allsky/tmp directory in memory instead of on the disk. This directory holds temporary Allsky files and is where most Allsky files are initially written to. Putting the directory in memory significantly reduces the number of writes to the SD card, which increases its life.

During installation you'll be notified of any actions you need to take when the installation completes. If there are any such actions, the first time Allsky runs after the reboot it will stop and display a message in the WebUI (which you should clear when done performing the actions).

The installation may take up to an hour, depending on how many package you already have installed and the speed of your Pi. Subsequent installations of Allsky will be significantly faster.

After installation, reboot if told to, then perform any actions the installation script identified. Allsky will not begin until you do the following:

1. Bring up the WebUI by entering http://allsky.local or http://allsky.localhost in a web browser. The default username is admin and the default password is secret.

   If your website is publically viewable you should change the username and password via the Change Password link on the WebUI.

2. Go to the Allsky Settings page.
3. Make any necessary and/or desired changes.
4. Click on the Save changes button. Allsky will start.

Allsky starts automatically when the Raspberry Pi boots up. To enable or disable this behavior, use these commands:

sudo systemctl enable allsky     # starts Allsky when the Pi boots up
#   OR
sudo systemctl disable allsky    # does NOT automatically start Allsky

When you want to manually start, stop, or restart Allsky, or obtain status, use one of these commands:

sudo systemctl start allsky
sudo systemctl stop allsky
sudo systemctl restart allsky
sudo systemctl status allsky

Tip: Add lines like the following to ~/.bashrc to save typing:

alias start='sudo systemctl start allsky'

You then only need to type start to start Allsky. Do this for the other commands as well.

Starting Allsky from the terminal is a great way to track down issues as it provides debug information to the terminal window. To start Allsky manually, run:

sudo systemctl stop allsky
cd ~/allsky
./allsky.sh

If you are using a desktop environment (Pixel, Mate, LXDE, etc.) or using remote desktop or VNC, you can add the --preview argument to show the images the program is currently saving in a separate window:

./allsky.sh --preview