• Naomikho@monyet.cc
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Yep, honestly I had no idea what I was cooking for the past two weeks lmao and it’s just testing and fixing and testing and fixing 🤣

      At least now I have experience on writing new applications and configuring stuff on the go, because I don’t have that kind of opportunity at my job.

      • ruk_n_rul@monyet.cc
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        not sure whether to cook my own or let you finish cooking. i just want to schedule posts (weekly thread).

        • Naomikho@monyet.cc
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          The feature is actually already done on my side(so I can just add in new post scheduling jobs). I’m just letting it do a test run on dev to see if there’s anything messed up with the cron scheduling and db table locking.

          • zen@monyet.cc
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            you’re accessing the lemmy db directly instead of using the lemmy api? (or on second reading, perhaps your code uses its own separate db to keep track of things?)

            • Naomikho@monyet.cc
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              I’m using the api, but I’m also using a database schema to store data that is specifically used by the bot.

      • zen@monyet.cc
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        is it in typescript? do you have any intention of releasing the code?

        • Naomikho@monyet.cc
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Yeah it’s typescript. JavaScript just gives me anxiety nowadays.

          The repo is private now, but idm making it public. I’m not sure how though as the repo(which is owned by another dev) is under our organization, which is private.

          • zen@monyet.cc
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            you could just git push it to a new repo, unless it is not git, or maybe your organization has something that prevents that.

            • Naomikho@monyet.cc
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Hmm, let me bring it up in the discussion later. It’s not impossible to just open a new repo, but it’ll be kinda pointless imo to open another one