Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Curt J. Sampson
    @0cjs
    Broken build script! Fire the developer!
    sssjjjnnn
    @sssjjjnnn
    Before I get fired, I'm going to push some code to handle wiki redirects and put something in the current meeting links
    Curt J. Sampson
    @0cjs
    That's probably my code, actually. I guess that somewhere in Test~ between thecd "$basedir"and runningstack` it changes the directory again. But I don't see how....
    sssjjjnnn
    @sssjjjnnn
    I was running the site-compiler manually
    Test script is probably fine
    Curt J. Sampson
    @0cjs
    Oh, yeah, then that's your problem.
    sssjjjnnn
    @sssjjjnnn
    I think a lot of that Haskell code could be written in a better way, but I'm not sure how. Maybe we can go over it a bit when you're feeling better
    It took me forever to turn the >>= into a do block
    Curt J. Sampson
    @0cjs
    Yes, I'd like to do that.
    sssjjjnnn
    @sssjjjnnn
    Should we turn on https now that the domain is pointing to Netlify?
    Curt J. Sampson
    @0cjs
    Getting started with that would probably be a good idea. I don't think it's as simple as just flipping a switch in the Netlify control panel.
    sssjjjnnn
    @sssjjjnnn
    Should I flip the switch and see what happens?
    The button is right there staring at me tempting me to push it
    Curt J. Sampson
    @0cjs
    Have you read the docs?
    If not, well, what could go wrong? Do it! :-)
    sssjjjnnn
    @sssjjjnnn
    I'm reading something that says "We’re ready to provision a TLS certificate from Let’s Encrypt and install it on our CDN."
    Are you being sarcastic? My default approach would be to click it and see what happens. HTTPS doesn't work now, so I doubt it will get any more broken
    "HTTPS was a one-click setup included in the price of $0, even on custom domains"
    Curt J. Sampson
    @0cjs
    Well, if basically anybody can get a certificate from LE for any domain with no proof that they own or control that domain, TLS is not terribly useful. And yes, I was being sarcastic. I tend to default to "find out what could break" before pushing buttons.
    And yes, it could get more broken. If it set HSTS headers, people might be unable to use the HTTP site for a long time.
    sssjjjnnn
    @sssjjjnnn
    Just checked the docs, looks pretty straightforward to me. It doesn't enable HSTS, you have to do that manually
    And of course not anybody can get a cert, but Netlify can because they are serving HTTP on the domain
    Curt J. Sampson
    @0cjs
    Sounds like it might be worth trying then, if it looks safe. (I couldn't recall if getting a LE cert involved changing anything in the DNS.)
    sssjjjnnn
    @sssjjjnnn
    I'd say it looks pretty safe, I'll give it a try.
    It said the DNS verification completed, but then failed to get the cert
    sssjjjnnn
    @sssjjjnnn
    Though it seem to have actually worked despite the error message
    Curt J. Sampson
    @0cjs
    Nice!
    Edward Middleton
    @E14n_twitter
    LE works pretty well, you can verified by a number of methods but the default doesn't need DNS record changes. https://en.wikipedia.org/wiki/Automated_Certificate_Management_Environment
    Curt J. Sampson
    @0cjs
    @ragga Do you mind making sure that everything you've backed up has a copy in the akari.tlug.jp repo? (Or everything that reasonably belongs there. That includes config files related to any web services.) This will ensure a reasonably large group of responsible people have access to this information.
    Henri "Ragga" Servomaa
    @ragga
    @0cjs yeah, I'll go through them.
    Curt J. Sampson
    @0cjs
    Thanks!
    sssjjjnnn
    @sssjjjnnn
    The PHP code is missing some plugins, m17n and xmldb and maybe others
    Curt J. Sampson
    @0cjs
    Huh? Can you expand on that a bit?
    sssjjjnnn
    @sssjjjnnn
    This is what I noticed, there may be others:
    define (TLUG_INCLUDE_PATH, '/usr/local/apache/php-include/');
    require_once ('m17n.php');
    require_once(TLUG_INCLUDE_PATH . 'carrubbers/xmldb.php');
    Curt J. Sampson
    @0cjs
    Right, ok. So why would that make any difference? Seems to me "can't be run at all because no PHP interpreter" doesn't change if we add the plugins. :-)
    sssjjjnnn
    @sssjjjnnn
    They can't be generated dynamically, but they're mostly static and could be generated at build time
    Anyway, if we want a complete archive of the old stuff, they're missing
    Curt J. Sampson
    @0cjs
    Oh! What a great idea!
    And yeah, I guess it's easier to grab whatever versions are on the old server than to figure out what those versions were and get them from alternate locations. But I'm guessing it's too late because the server's gone? But I think someone has a backup?
    Curt J. Sampson
    @0cjs
    I restored building and running the test for the TLUG.Hello and TLUG.HelloTest modules. @sssjjjnnn, it looks as if you'd just accidentally commented-out/removed the code that built and ran that?
    Curt J. Sampson
    @0cjs
    Also, I wonder if it makes sense to rename Test to Build, both because most people will not be concerned that it's testing things (though of course it still would) and because it reduces the now-3 chars needed for tab completion since we added template/ back down to 2 chars.
    sssjjjnnn
    @sssjjjnnn
    What's TLUG.Hello? The build was getting kind of slow for me, so I didn't want any unnecessary stuff in there.
    I prefer "Build". Running tests always seemed part of the overall build process to me. So "Test" is a bit ambiguous as to whether it will also do a full build, or just run the test phase of the build.
    Curt J. Sampson
    @0cjs

    From the tlug/tlug.jp@8d857a7:

    TLUG.Hello and its test are simple tests originally added to demonsrate [sic] that the test framework actually works. It's an open question as to whether these are actually still needed, but they do serve as a handy, simple example and as something to tweak when playing around with Haskell.

    I'm open to ways to clarify this, which maybe even we should add as a comment to the files.
    I'm surprised it was slowing you down; is something wrong with the build that the dependency check (followed by not recompiling it) was slow? Or was that just a random change that you hoped would optimize things but didn't? :-)

    sssjjjnnn
    @sssjjjnnn
    I was in a hurry and just hoping it would help. The build is still a bit slow. I think there's enough stuff in there now to demonstrate that the test framework works, but they could be useful as a simple example
    sssjjjnnn
    @sssjjjnnn
    I'm normally not so sloppy, just been really busy with work and have been doing this TLUG stuff in a big rush
    Curt J. Sampson
    @0cjs
    No problem. Obviously we have some real-world constraints working against us here, but so long as we are doing the best we can within them, and know how to improve things when we get more time or whatever, it's the best that it can be.
    Anyway, my current thought on TLUG.Hello is to keep it because I think it makes a good place to start for non-Haskell developers wanting to start playing with our code here. But I'm open to counterarguments. I don't think that compilation speed is one, though, because it's a pretty small fraction of an initial compile and nearly infitesimal in subsequent compiles when it's not modified.
    sssjjjnnn
    @sssjjjnnn
    Okay, let's keep it then.
    Curt J. Sampson
    @0cjs
    @E14n_twitter Looks like you forgot to push the master branch when you made the site change. Your changes will vanish next time someone else commits a change unless you push that up.
    matrixbot
    @matrixbot
    KCinJP Anyone going to the オープンソースカンファレンス on the 21st (Fri) & 22nd (Sat) of this month?
    https://www.ospn.jp/osc2020-spring/