Nooope: Looks like this is due to the way arachne does things. This should have been so easy! lol

@georgek Hello! I’m here for a bit.

Can I help with any questions?

Oh hi! Thanks, actually nope, hence the last comment. Arachne has its own world and, being new, doesn’t always play nice with others. The last wall was some deep spec-driven thing from inside arachne’s runtime.

I’m getting help from luke to get things fully integrated but def. not anything to do with Onyx

🙂

I was Sooooo close.

hahahaha

nope

Sweet, glad to hear you’re almost over the hurdle!

Thanks! fingers crossed

haha

⚔️

Best I got.

Almost did emoji for middle finger by accident. Whole different can of worms

Hahahaha, either would have been great

There should be a D&D emoji set

That should totally be in it

Hah

So this is a really newbie question around how to structure projects for setting up a system. I just encountered the lein onyx template. It looks peer-oriented but it does have affordances to submit jobs. I’ve been going the whole route with spinning up an env, peer group, and peers. My question: In a typical deployment you need kinda both if you want a server entrypoint that provides a REST api to submit jobs right (if you want to organize your projects this way)?

Or am I missing something basic? (totally wouldn’t be surprised)

@georgek Yeah we’ve seen a lot of different set ups. For what I know about your situation, you’d probably want to search through the idioms in the template and bring them back into your own project.

Thanks, there’s some new really nice stuff in there. Sounds good!

For sure!