waterkip / act Goto Github PK

I've changed the logic a bit, but it might be broken for older users who haven't changed their password in a decade or so (or whenever they went from MD5 to BCRYPT).

• act
• database
• mail
• wiki?
• other stuff - wait and see what happens

because fancy stuf is nice

A database dump of a wiki would be nice to have, so we can create a DB and populate it.

This is kind of a stupid requirement, I know, but very much needed.

This seems to be more work.

• There are some tests that test the setup of your current installation and not the code itself. This needs to go IMO. The code needs to work as expected. The testsuite shouldn't validate that you have a working installation, this should be done in the code by die-ing early and validating the configuration on startup.

• There are some tests that check all the dependencies, this can be automated via dzil for example to generate a Makefile.PL and a cpanfile

• The tests use t/Util.pm, move to t/lib and use Test::Lib for those instances

• Maybe create t/lib/Act.pm and put some sane defaults in there (use Test::More or Most) and be done, reduces boilerplating in .t files

Act now stores photo's somewhere in the $Config->root folder based on
die dir_photo variable found in the configuration. This allows pictures to be stored on "normal" machines, but with Docker one would put these either Swift, S3 or on a volume in order to be able to keep the data after a container restart.

Move logic to allow for absolute paths?

This seem to be a bit broken now?

I like the pun :)

Maybe we should call this "project" act two - just thinking out loud

For now, just follow: https://github.com/Act-Voyager/Act-out-of-the-box/blob/master/step-by-step-rescue

Probably something in the Act::Dispatcher

Sometimes it doesn't work on the first run due to dependency ordering: fix this

Right now the conferences (https://github.com/Act-Conferences) have a pretty standard directory layout. Within Act itself these directories are split into other bits and pieces

$ tree -d nlpw2018
nlpw2018
├── actdocs
│   ├── conf
│   ├── static
│   │   └── tutorials
│   └── templates
│       ├── core
│       │   ├── bank
│       │   └── user
│       ├── custom
│       ├── menus
│       ├── payment
│       ├── texts
│       ├── tutorials
│       └── user
└── wwwdocs
├── css
└── img

Act (afaik) splits this up to:

actdocs => $ACT_HOME/actdocs/nlpw2018/
wwwdocs => $ACT_HOME/wwwdocs/nlpw2018

This is kinda bothersome in Docker, since you don't want to mount two folders for each conference (or, I wouldn't at least).

Any static file found in wwwdocs aren't show to the user.

The PSGI branch is a bit out of date with the master branch:

On branch psgi
Your branch and 'upstream/master' have diverged,
and have 143 and 196 different commits each, respectively.

What branch should become leading?

Easier for people who do SaaS Acts

a use Act::Config automaticly loads all the configuration files. I don't want this (or maybe I do, but things.

We can run one DB server on a docker instance. But the loading becomes a bit annoying due to the environment variable of the database in docker.

We can work around it by scripting it, but it would still require us to do some scripting based on configuration files found elsewhere...

What do the Act guys do in the real world? I think we should opt for multiple databases instances, but feel uncertain about it. What to do?

Should allow for even quicker things for Act conference people. Docker pull, mount files and test your thing.

Having multiple services in one container violates the Docker principal of running multple services in one container. Therefore, move it to somewhere else.

These files should be automaticly generated. It kind of prevents me from rebasing the branch because of the many changes during development where I just want things to well... not interfere with the actual code I'm rebasing.