ill_logic has quit [Remote host closed the connection]
ill_logic__ has joined #sandstorm
aldeka_limechat has quit [Ping timeout: 240 seconds]
ill_logic_ has quit [Ping timeout: 256 seconds]
ill_logic has joined #sandstorm
ill_logic__ has left #sandstorm [#sandstorm]
sydney_untangle has joined #sandstorm
afuentes has quit [Ping timeout: 240 seconds]
BlueNinja has joined #sandstorm
ill_logic__ has joined #sandstorm
ill_logic has quit [Remote host closed the connection]
jemc has joined #sandstorm
ill_logic__ has quit [Ping timeout: 245 seconds]
wolcen has quit [Quit: Leaving]
aldeka_limechat has joined #sandstorm
aldeka_limechat has quit [Ping timeout: 245 seconds]
<ocdtrekkie>
Okay, so, I tried to add import/export to Scrumblr, and the download isn't working in Sandstorm. It does work correctly if I open the grain frame in a new tab.
<ocdtrekkie>
vagrant-spk is more helpful in terms of including support for different platform stacks, and since it uses a vagrant VM as the execution environment, it can be run on Windows and OS X.
<ocdtrekkie>
spk can only run on a Linux machine which is running Sandstorm.
<ill_logic>
I see.
<ill_logic>
thx
<ocdtrekkie>
no prob
<ill_logic>
Another question - is there any chance the baseline will be anything newer than Debian Jesse?
<ill_logic>
Or has unstable always been an option, and I just wasted weeks trying to get these dependencies to build
<ocdtrekkie>
I personally have no idea what would be involving in changing vagrant-spk's baseline.
aldeka_limechat has joined #sandstorm
aldeka_limechat has quit [Ping timeout: 276 seconds]
<ocdtrekkie>
vagrant-spk appears to pin a specific version of debian-jessie, ill_logic, because the next revision after it removes support for vboxsf, which vagrant-spk seems to require.
<ocdtrekkie>
So I am not sure if you are wasting time or not waiting for updates to it.
<ocdtrekkie>
asheesh is the human most likely to have the best answer to your question.
<TonyTheLion>
> Error: couldn't add user: not authorized on admin to execute command
<TonyTheLion>
mongodb refusing to add the "sandstorm" user
<Dynamic>
ahh
<TonyTheLion>
and then failing
<Dynamic>
im stuck on the wildcard error
<Dynamic>
wait
<TonyTheLion>
did you find something?
<Dynamic>
yup
<Dynamic>
my isp is stopping me
<Dynamic>
im self hosting a local server and have it DMZ'd
<Dynamic>
gues they dont like that
aeternity has quit [Ping timeout: 240 seconds]
<TonyTheLion>
why would they stop it?
<Dynamic>
because in my DNS settings from where I can configure the settings, i have a wildcard entry for the domain name I bought
<Dynamic>
*.example.com
<Dynamic>
which if looking at the hosts
<TonyTheLion>
question is why would your ISP care about that?
<Dynamic>
goes to 192.64.119.254
<Dynamic>
which has to be in their network
<Dynamic>
because it sure isnt mine
aeternity has joined #sandstorm
<Dynamic>
I wonder if I paid for a static IP if that would solve this
<Dynamic>
for now I just feel stuck
<kentonv>
TonyTheLion, are you using a hosting provider? If so, which one? Also, which distro, what kind of machine, etc.? My hope is that I can reproduce the problem myself.
<TonyTheLion>
I'm tempted to say that its more likely that you have a misconfig somewhere
<TonyTheLion>
rather than your ISP blocking that wildcard DNS
<Dynamic>
ill get my config
<TonyTheLion>
kentonv: its a linux Ubuntu 16.04 LTS machine. Its self hosted