Jerry avatar

Jerry

@Jerry@kbin.social

I'm a guy who likes to play with Linux and the cloud. I work in IT for a bank. I'm a liberal. I'm constantly trying to learn new skills.

Owner of:
Mastodon: https://hear-me.social
Calckey: https://bostonsocial.online
Peerview: https://my-sunshine.video

he/him/his

rmattila74, to mastodon
@rmattila74@energydon.fi avatar

A simple thing that would make more welcoming to new users: make the Global timeline as the default view instead of Home.

Jerry,
Jerry avatar

@rmattila74 I like this idea

mikelovesbikes, to mastodon
@mikelovesbikes@hear-me.social avatar

Anyone know any instances that don't store your IP address for ("up to") a year?

Jerry,
Jerry avatar

@mikelovesbikes Any server that is behind Cloudflare won't get your IP address, just the IP address of the Cloudflare proxy server that you came in from. hear-me.social, the instance that you are on, is behind Cloudflare and so your IP address is never being captured, so never saved.

When I log into the server, my IP address is recorded as 162.158.63.162 which is the Newark, NJ Cloudflare proxy server. I'm actually connecting from Boston. But, for some reason, at the moment, Comcast is co-locating me to Newark, and not their Boston location, so I enter Cloudflare from their Newark proxy. Clearly, I would not be traceable.

Jerry, to kbinDevlog
Jerry avatar

Has anyone tried creating a KBIN server using the Docker instructions since Saturday? I got a development server running on Saturday and I decided to bring up a production ready version on Sunday, but now I'm running into two errors while creating it.

First:

In these instructions:

$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env

There is no directory "var" so the chown fails

Second:

When running docker compose build --pull --no-cache

It now fails with this:

=> [php app_php 20/21] RUN rm -Rf docker/ 0.2s
=> ERROR [php app_php 21/21] RUN set -eux; mkdir -p var/cache var/log; if [ -f composer.json ]; then composer dump-autoload --classmap-authoritative --no-dev; compose ...

This also seems to relate to the var directory, and so must be part of a recent change in the build that relates to the var directory.

Can anyone help?

Thanks

Jerry,
Jerry avatar

I tried today. I built a test instance that seems to mostly be working. But, one problem I'm facing is that images are not going into the S3 bucket and I think the reason is that KBIN doesn't know the endpoint URL, which in my case is s3.wasabisys.com and I cannot find anywhere where this is specified. It keeps sending the files to the https://<instance URL>/media when it should be sending them to wasabi.

I'm also having some federation issues. If I search for magazines and users on this new instance from Mastodon, they are found. But if I follow a magazine or user, Mastodon doesn't get notified. Unsure what the issues are. I've just got this up a few hours ago.

Have you tried to set one up?

Jerry, to kbinDevlog
Jerry avatar

Wow, my first post on KBIN! Watch me screw it up somehow.

I'm going to try to bring up a KBIN server tomorrow (emphasize on "try"). I've somehow managed to get Mastodon, Calckey and Peerview servers going using just enough knowledge to be dangerous, and I've amazed myself.

The KBIN documentation for building a server is bare bones so I hope I can figure out what to do.

Has anyone stood up a KBIN server and do you have any tips, warnings, advice?

Thanks

Jerry,
Jerry avatar

@ernest Thank you! Would it be possible to add some information on using an S3 bucket for storage, if it's possible to do so?

Jerry,
Jerry avatar

Has anyone tried creating a KBIN server using the Docker instructions since Saturday? I got a development server running on Saturday and I decided to bring up a production ready version on Sunday, but now I'm running into two errors while creating it.

First:

In these instructions:

$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env

There is no directory "var" so the chown fails

Second:

When running docker compose build --pull --no-cache

It now fails with this:

=> [php app_php 20/21] RUN rm -Rf docker/ 0.2s
=> ERROR [php app_php 21/21] RUN set -eux; mkdir -p var/cache var/log; if [ -f composer.json ]; then composer dump-autoload --classmap-authoritative --no-dev; compose ...

This also seems to relate to the var directory, and so must be part of a recent change in the build that relates to the var directory.

Can anyone help?

Thanks

  • All
  • Subscribed
  • Moderated
  • Favorites
  • โ€ข
  • normalnudes
  • mdbf
  • ngwrru68w68
  • thenastyranch
  • magazineikmin
  • hgfsjryuu7
  • DreamBathrooms
  • Youngstown
  • slotface
  • ethstaker
  • PowerRangers
  • everett
  • kavyap
  • rosin
  • anitta
  • vwfavf
  • osvaldo12
  • InstantRegret
  • cisconetworking
  • tacticalgear
  • cubers
  • khanakhh
  • Durango
  • GTA5RPClips
  • Leos
  • tester
  • modclub
  • provamag3
  • All magazines
    •