getting started: a few hiccups about brutalinks HOT 3 CLOSED

Thank you for your feedback @faried. I implemented some the changes you proposed. (The ActivityPub tables in the init.sql file are not yet used anywhere in the code, I have committed them already to iterate over the structure a bit)

One of the problems you encountered is due to the fact that I'm using a load balancer in front of the application (see why below) which listens on port 80 for the host in HOSTNAME. I probably should document this. You can change add in your config:

API_URL=http://localhost:3001/api

Besides that I think the problems you encountered running the app could be solved by a recent commit where I started using godotenv. Now if the .env or .env.{dev,qa,prod} files exist in your run directory, they are loaded without requiring to export all the values beforehand. So now it would suffice to run make run

I won't integrate the port changes you made, because I designed this application as a TLS agnostic application, basically relying on the load balancer to handle HTTPS.

This would allow someone to run multiple applications on different ports in the same environment and round-robin the proxy connections. In the same idea, but on a longer term, the frontend and api packages will evolve into being their own separate applications that will need to be run at the same time. This will most likely be handled by listening on different ports, but I'll see when I get there.

So, in conclusion, please try again with a more recent version (past commit bc39961) and let me know what problems you still encounter.

from brutalinks.

Thanks. I removed my changes, pulled, and got 0281345. It works now.

Do you have a roadmap for littr? A list of features you'd like it to have before people can use it publicly?

from brutalinks.

I have a roadmap in my head, but unfortunately I'm lazy at everything else but programming when it comes to a project.

A pseudo-roadmap can be seen in the milestones section.

What I would like to get done before doing a "soft launch" is:

Adding OAuth support to AP endpoint.
Frontend authenticating as OAuth application to AP endpoint.
Full frontend functionality provided through AP (C2S).
Adding federation (S2S) support between littr.me instances for submissions and comments.
Adding support for some basic moderation mechanisms (reporting, blocking, etc).

As a bonus I would like also to abstract most of the ActivityPub handlers and middlewares to the go-ap/activitypub.

from brutalinks.