Can I get some alpha testers for my 30040/30041 uploader?

I catch a lot of errors, but I need more tests and it's probably sorta buggy.

ANYONE WITH A MARKDOWN FILE IN THE HOUSE?

Thanks in advance? šŸ¤™

https://gitworkshop.dev/repo/eBookUtility

Reply to this note

Please Login to reply.

Discussion

1000 sats each, to the first 10 people who try it out and give me a quick review.

Give me the feedback on gitworkshop, if you can.

hah i knew you'd ask when i read it

ok, but what am i doing?

Just need to install php and composer, if you don't already have it, I think. Then just follow the directions in the readme.md.

It's possible that you'll also need to download the https://github.com/nostrver-se/nostr-php library, but I don't even know. I've never built something like this, before. Stuff like that is what I'm trying to figure out.

i don't know this php stuff since literally 2003

i will have a look at it because you be coo

ok i have php and compos000r and all the shizl but what do i do to test this exactly?

also i be dumb for the phpee

wat now?

were is createBook.php exactly? did i clone it?

PHP Warning: include_once(/home/me/Documents/eBookUtility/vendor/autoload.php): Failed to open stream: No such file or directory in /home/me/Documents/eBookUtility/createBook.php on line 3

PHP Warning: include_once(): Failed opening '/home/me/Documents/eBookUtility/vendor/autoload.php' for inclusion (include_path='.:/usr/share/php') in /home/me/Documents/eBookUtility/createBook.php on line 3

PHP Fatal error: Uncaught Error: Class "swentel\nostr\Event\Event" not found in /home/me/Documents/eBookUtility/src/BookEvent.php:61

Stack trace:

#0 /home/me/Documents/eBookUtility/src/BookEvent.php(151): BookEvent->create_articles()

#1 /home/me/Documents/eBookUtility/createBook.php(14): BookEvent->publish_book()

#2 {main}

thrown in /home/me/Documents/eBookUtility/src/BookEvent.php on line 61

i dang broked it

seriously, you need to work on your documentation howtoo thing

Yeah, I need someone to tell me what to write in it. šŸ™ˆ šŸ˜…

No, this is the part I'm not really sure about. vendor folder includes all of the dependencies.

nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe How does that work, when someone else is installing it?

yeah, i love vendors folders

your gitignore blocked it from being uploaded

and now you are in gitignore hell

Oh dear.

Should I upload it or would an install script be better?

Install would probably be better, since it doesn't assume you have composer setup.

yes, you can probably assume php installed, point to directions for that for ubuntu/debian and the rest can go to hell, oh yeah, where we are

but then make a script with like

#/usr/bin/bash

things here

Those are managed with composer.

Nostr-php only contains the composer.json (so no composer.lock file) so you're always downloading the latest version of the dependencies defined in that composer.json file.

To update your existing project, run `composer update -W`

If you're still stuck, remove the vendor map first with `rm -rf vendor` and run `composer install`

testing

i've lost track of what i'm doing

need hamburger

I keep zapping you, but it doesn't go through.

weird, i get zaps from many others all the time that i don't comprehend

Your zap button is grayed out, on Nostrudel, and Freerse just shrugs.

oh i changed my lnurl

it's now mleku@getalby.com

better change my profile event

yeah i did

on nostrudel go to my profile and it should load the new

Did you pull the commit I just pushed?

It should be in the root folder. It hardly does anything, just a way to start the app.

just checked, no new commits

ran git pull and nothing new and this is my git log:

commit 6b0c75843068c96e3a9741fcd2669642baa9c9f7 (HEAD -> main, origin/main, origin/HEAD)

Author: Sebastix

Date: Thu Jul 4 16:39:50 2024 +0200

remove website dir from library repo

commit 2fe0a631af837043f47223d46abb816c946c57e0 (tag: 1.3.3)

Author: Sebastix

Date: Thu Jul 4 16:11:25 2024 +0200

* add backwards compatibility in the __construct() of relay for the $message argument which was used in version < 1.2.4

* fix WebsocketClient response (message) which returned an array instead of a string for the json_decode function

I think that's the Nostr PHP Helper library, not mine. šŸ¤”

For anyone who has Word Documents there is a tool. https://word2md.com/

I also sometimes copy-paste stuff into https://stackedit.io/app# or habla.news and format it. Just need the two header levels (# book title ## chapter title) and then save the content to an .md file (a .txt file that you rename).

Obsidian is also great for this.

Seems to work. Had to move the **Abstract** to ## Abstract and ### References to ## References, but the content worked.

https://njump.me/nevent1qqsz6vj2zsej45e9meyx5k5x33crhdfpqnmd82pw9dw2feygsj6p32qprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqgs9wd35keyxxn966y8jg5thvzy75ggfpk2q0ac4aq79w76xzxhxahqy9p7mu

So, we've got the Bible, Aesop's Fables, and the Bitcoin Whitepaper, so far. šŸ˜€

Slowly slowly all of sacred-texts and ccel catalogue lol

Wait until you see nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn pretty web app. Then we can actually read the files, rather than just writing them.

We do have the entire Western canon as a target.

The challenge will be making sure we can see each others' books, so that we don't all upload the same ones.

I found that it didn't like colons in the title, and like you said, `**Abstract**...` needed to be a heading level 2. I also found that the `## Abstract ...` needs to be broken up, not just made into a heading (saw the `\n\n` in your event published). Otherwise, the article event fails to create (that was the last key to making it work).

Some checks might be needed to provide the user feedback on what might have caused a book to fail to publish.

Ah, you mean like how I moved the text before Abstract to after?

Looks like you're relay didn't write. I have a check for that and one redo.

Ah, you're right. The first article event is a bit off, as Abstract should be the title, not the beginning of the paragraph. Hmm... good catch.

Getting the white paper right is a good test data set. That'll keep me busy, for a while.

I just explode on the ## and then pop off the first element for a title and trim.

I don't even look what's in-between.

Added an issue.

That's actually pretty cool! I get ngit notifications in Amethyst. I mean, it's obvious why, but it's still a novelty to have a more unified notifications system.

😊 Yeah, I love it.

Add a composer.json file for managing your dependencies, like the nostr-php lib šŸ˜‰

https://codewithsusan.com/notes/composer-in-plain-php

I have one, in the src folder. I'll move it up to the top.

Aah! Yes, the root dir of the project is a better place.

I hope I can find some time tonight to have a quick view on it and install + test it.

That would be great!

This is a kind of practice-run, as we wanted to test out PHP with Nostr, anyway, so I grabbed the opportunity and learnt to code in 3 minutes. šŸ˜‰

i recommend you have some test environment to check your destructions work

a virtual machine is probably the cheapest way, but if you have a second computer that is retarded that's a good option also

been thinking about re-deploying my ol' lenovo laptop as a third screen and backup in case of power outage, plus also windows test rig

hell, might just get on that, today seems to be my day of receiving new things to make my hardware to adequate

I'm actually going to get a new laptop, soon, as my husband is finally taking pity on me. šŸ˜… I can then use my netbook for testing. Also great, because it's worst-case, from performance.

It has! I never appreciated how fucking inefficient everything is.

I can't even use some of the Nostr apps.

i'll just qualify it with this:

hate towards evil is goodness

Check out https://ddev.com for this

Oh God I hate Docker. šŸ˜‚

It should make it easier šŸ˜… I’m still doing all the Docker stuff on my own for every project..

You could have a look at Nix as well perhaps

We used to do everything in Docker.

What do you use now? šŸ¤“

An Asus EEE PC seashell that would implode, if I started running docker on it. šŸ˜‚

I'm giving a go at testing the uploader, however getting Composer configured is proving to be a nuisance to me and a roadblock. šŸ˜• Still trying.

I'm doing something wrong. I see no "user" folder.

Whoa, that is weird. šŸ¤”

Is this the repo you're pulling from?

https://github.com/SilberWitch/eBookUtility

No, I didn't pull from any repo! I added git clone https://github.com/SilberWitch/eBookUtility to the start of my steps. That solved the lack of user directory, so that's good. Getting errors on composer install now though (can't generate composer.lock). I'll try again tomorrow maybe.

Maybe start from scratch again, this time cloning the repo, first, then composer install.

Getting closer. Tried in two places, local and VPS. On VPS, can't get over php extension errors (tried installing, no luck). On local laptop, got things installed that were headaches yesterday (composer, extensions) and things seem to be working. But "article eventID was not created" so, hmm.

That's the relay writing error from me. I should make it more clear.

nevent1qqsvxtz0xg7g4drlrzujvge6s9f7lnaavt3e5t47pa82gqqqnqzfefqzyq5jzeu977eyrfhthv843ul03q44gnd050mqejnxd25ytsf2vd48qqaqxmm

https://njump.me/nevent1qqsvxtz0xg7g4drlrzujvge6s9f7lnaavt3e5t47pa82gqqqnqzfefqzyq5jzeu977eyrfhthv843ul03q44gnd050mqejnxd25ytsf2vd48qqaqxmm

šŸ˜… Oh dear. That came out a hot mess. Do you have the original, to share? So that I can add it to my test data set?

How was the installation procedure?

Flawless 😃

That's a relief. šŸ˜…

Everyone else is like 😱

Ah, I see, it's like with the Bitcoin Whitepaper, that it has text between the # and the first ##. None of my examples had that, but I just need to control for it and shove a "## Preface" tag in-between. Thanks!