All of lore.kernel.org
 help / color / mirror / Atom feed
From: "A. Schulze" <sca@andreasschulze.de>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] server switch over
Date: Sun, 01 May 2022 17:18:05 +0000	[thread overview]
Message-ID: <cc781fc7-c3c6-77c8-e0e5-7ac968d73cd1@andreasschulze.de> (raw)
In-Reply-To: <20210125220841.qhrji7b77obenbu6@gpm.stappers.nl>



Am 01.05.22 um 11:16 schrieb Wolf Bergenheim:
> After sum huffing and puffing I have gotten the main site back up, and also, most importantly, the mlmmj.org <http://mlmmj.org> lists up and running again.
> 
> Thank you to all who helped!
> 
> There are still some sub--parts of the website not working quite correctly, and here is where I'd like to know more from you. Is it worth fixing those, or should I somehow (?) edit the website to point to the gitlab? Where is development happening nowadays? Where are issues being tracked? Is it all happening on gitlab?
> 
> Also if someone wants access to the web server reach out to me I can add your ssh key to the mlmmj user so you can ssh into the server.

Hello Wolf,

Thanks for your effort to get mlmmj.org up & running again.
I looks like the domain should receive some further care: https://www.hardenize.com/report/mlmmj.org/1651425079

I may have a look at the servers an suggest / implement improvements. If this is desired, please add
https://andreasschulze.de/authorized_keys

Andreas

(also running mlmmj at dnswl.org)


  parent reply	other threads:[~2022-05-01 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 22:08 [mlmmj] server switch over Geert Stappers
2021-01-26  0:15 ` Mads Martin Jørgensen
2021-01-26  8:26 ` Christof Thalhofer
2021-01-26 13:30 ` Mads Martin Jørgensen
2021-01-26 15:13 ` jf-mlmmj
2021-01-26 17:32 ` Christian Stærk
2021-01-26 18:55 ` A. Schulze
2021-01-26 19:34 ` Piotr Auksztulewicz
2021-01-27  9:18 ` Christof Thalhofer
2022-05-01  9:16 ` Wolf Bergenheim
2022-05-01 17:18 ` A. Schulze [this message]
2023-02-11 20:25 ` Wolf Bergenheim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc781fc7-c3c6-77c8-e0e5-7ac968d73cd1@andreasschulze.de \
    --to=sca@andreasschulze.de \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.