2020-04-29 - Re: Initial installable Dev packages for V4

Header Data

From: Tim <ti***8@gmail.com>
Message Hash: 716dbb077e0c01cacacc1ca6fa7a6f72882fb3f304dd16dca4c8c2894ab95132
Message ID: <CAESLx0JDRJdf25apEAfKwPB1fWoGDMaGqc7v9K6p-fzpKA=D6w@mail.gmail.com>
Reply To: <CAESLx0+wdvAyXPmL__tb6+KYGHf0gDJ8UWvVz90UeCpA142Tig@mail.gmail.com>
UTC Datetime: 2020-04-29 07:36:11 UTC
Raw Date: Wed, 29 Apr 2020 22:36:11 +0800

Raw message 

Still not a beta build, but the current packages should work a bit better,
and let you modify settings (Advanced Settings) so you can configure the
Coova Chilli interface for some testing.

All the basics should be working at this stage. You should be able to
create groups/users, edit them, login, etc.

I've updated the instructions a little after testing from a clean 18.04
install
1. Clean install Ubuntu 18.04
2. Point to new Grase development apt repo
$ echo deb https://apt.grasehotspot.org/dev bionic main | sudo tee
/etc/apt/sources.list.d/grase.list
3. Get the repo key
$ sudo wget
https://github.com/GraseHotspot/grase-repo/raw/master/key/grase.hotspot.2020.gpg
-O /etc/apt/trusted.gpg.d/grase.hotspot.2020.gpg
4. Update your apt information
$ sudo apt update
5. Install the required Grase packages. As part of the install, there are a
few database questions, just accept the defaults
$ sudo apt install grase-www-portal
$ sudo apt install grase-conf-freeradius grase-conf-dnsmasq coova-chilli
6. You should now have a Grase install accessible. e.g.
http://127.0.0.1/grase/

There is still something weird going on with the initial DB install from
the grase-www-portal package, so I'll work on that this week to try and get
that packaging issue resolved.

After the install, you'll want to setup the network interfaces (See
http://127.0.0.1/grase/settings/advanced/ and modify networkLanInterface
and networkWanInterface) and then reboot.

I'll do more testing on the coovachilli/freeradius integration parts this
weekend, they were working last month, but with lots of packaging changes,
them installing isn't the same as them working :-P

I look forward to feedback from testing, the main feedback, for now, is
things that don't work. There will be lots of rough edges, untranslated
strings etc, but for V4 we're aiming to get something out that works so
people having issues with an old install who need to upgrade have an option
to upgrade to.

Regards

Tim


On Tue, 4 Feb 2020 at 22:24, Tim <ti***8@gmail.com> wrote:

> So these instructions are going to be brief, as they are intended for
> people somewhat comfortable with setting up / running packages under Linux.
> This is still a development version, things will be broken, please do not
> try and use this in production!!! In particular, parts of the Coova Chilli
> integration are not finished, and probably will not install 100% correctly
> (e.g. the network settings will be wrong). This development version allows
> you to start playing with the admin interface. There is also reduced
> functionality in many areas as I've migrated key components and lesser-used
> features will follow later (like manual locking of users, complicated
> time/data limits).
>
> 1. Clean install Ubuntu 18.04
> 2. Point to new Grase development apt repo
> $ echo deb https://apt.grasehotspot.org/dev bionic main | sudo tee
> /etc/apt/sources.list.d/grase.list
> 3. Update your apt information
> $ sudo apt update
> 4. Install the required Grase packages. As part of the install, there are
> a few database questions, just accept the defaults
> $ sudo apt install grase-www-portal grase-conf-freeradius
> grase-conf-dnsmasq coova-chilli
> 5. You should now have a Grase install accessible. e.g.
> http://127.0.0.1/grase/
>
> If you wish to test the migration from V3, please find your latest backup
> files of the database (they can be gzipped) and copy them to the new
> server, the run the following command, updating it to point to the backup
> files. It will delete all the current database contents and import the V3
> data and migrate it to V4
> $ sudo -u www-data /usr/share/grase/symfony4/bin/console
> grase:migrate-v3-backup ~/mysql_radius_backup.sql ~/mysql_radmin_backup.sql
>
> Just because you get things working on the development version, does not
> mean you'll be able to eventually upgrade it to a production server. I may
> still require breaking changes in database schema, and I will assume that
> we are making clean installs. When I actually get to alpha/beta releases, I
> will ensure that development installs can become production installs when
> V4 is released.
>
> Now that I have installable packages I'll put more effort into migrating
> the last of the settings configuration code, so that we can start testing
> CoovaChilli/Freeradius integration outside of my test setup.
>
> Regards
>
> Tim
>
>

Thread