Dev Mode: Change mastodon.dev to something that works #8684
Comments
|
I'm gussing my ag/grep overlooked hidden files. I was able to change the dev server dns by modifying it in .vagrant.env - probably something someone more experienced with vagrant would know. P.S. thank you so much for Mastodon. I enjoy making contributions to my local instance! I'm gonna leave this open, though. I don't feel like mastodon.dev is a sane default for Vagrant. I'll send a PR later. |
|
What would you suggest? |
|
i use .dev domains for my day-to-day work and i've never had a problem with
them.
…On Thu, Sep 13, 2018 at 5:26 PM Eugen Rochko ***@***.***> wrote:
What would you suggest?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8684 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAORV4xznvOf5pz7EvySqrqJpyKZLHnLks5uas2LgaJpZM4WmmiL>
.
|
|
@nightpool Awesome! I'm not sure the problem happens everywhere. However, I can reinforce my argument with the following: @Gargron I was going to go with .local or .test. I've got the .vagrant.env and the Vagrantfile situation figured out. I'm just not sure as to where the default dev admin account is created within the Ruby backend as I'm not strong with Ruby. If you give me a push, I'd be happy to do the work. Thanks for your responses! |
|
does local vagrant not have a ssl certificate? we could probably locally
generate one and have people add it to their local trust roots
…On Thu, Sep 13, 2018, 7:06 PM trevDev(); ***@***.***> wrote:
@nightpool <https://github.com/nightpool> Awesome! I'm not sure the
problem happens everywhere. However, I can reinforce my argument with the
following:
https://stackoverflow.com/questions/47809632/i-can-no-longer-access-my-local-development-dev-websites-in-chrome-http-is
https://www.theregister.co.uk/2017/11/29/google_dev_network/
https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd
@Gargron <https://github.com/Gargron> I was going to go with .local or
.test. I've got the .vagrant.env and the Vagrantfile situation figured out.
I'm just not sure as to where the default dev admin account is created
within the Ruby backend as I'm not strong with Ruby. If you give me a push,
I'd be happy to do the work.
Thanks for your responses!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8684 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAORV5U0-UOckz608U8FNItXgH__j_H7ks5uauTggaJpZM4WmmiL>
.
|
|
@nightpool: If heading in that direction, have a look at mkcert. |
|
Hold on, is there no better option than to use SSL on a local machine? That seems kinda pointless and overly complicated. Why do we even need a TLD, won't it work with localhost? |
|
@Gargron: TLS does indeed work with localhost, and I personally haven't found using TLS for local development to be overly complicated. As for why one would want to use TLS on a local workstation, one reason is that it is required for WebAuthn (successor to U2F), support for which I hope will someday land in Mastodon. 😁 |
|
the question was whether we needed a *TLD* for localhost, and the answer is
that because this ticket is specifically about vagrant development, yes, we
probably do. (maybe there's a way to do something similar to docker
"expose" stuff though?)
…On Sat, Sep 15, 2018, 3:35 AM Justin Mayer ***@***.***> wrote:
@Gargron <https://github.com/Gargron>: TLS does indeed work with
localhost, and I personally haven't found using TLS for local development
to be overly complicated. As for why one would want to use TLS on a local
workstation, one reason is that it is required for WebAuthn
<https://en.wikipedia.org/wiki/WebAuthn> (successor to U2F), support for
which I hope will someday land in Mastodon
<#562>. 😁
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8684 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAORVxlmoLjskUgpqGiYRH2LicxDxdCQks5ubK2ugaJpZM4WmmiL>
.
|
|
Literally just changing the domain name in the 2 vagrant config files and re-provisioning fixes the issue. I'll send a PR later tonight what'll include some commented out options to increase vagrant performance as well while I'm at it. |
|
Pull request sent. |
I have a local vagrant setup where I changed the hostname to mastodon.local so that my vagrant dev server would actually load. Google has done something crappy with .dev sites that breaks them on local machines. However, the mastodon server is still serving static assets from mastodon.dev.
I tried using ag/ripgrep to see if I could find any other configurations that set the dev server's dns to mastodon.dev, I couldn't find anything.
Is there any chance I may get some guidance with changing the mastodon vagrant dev dns or perhaps see the default changed in a PR?
master(If you're a user, don't worry about this).The text was updated successfully, but these errors were encountered: