write-ups | Write-ups on CTF challenges | Hacking library

The | and the missing port is most likely the problem. In ncat -l --exec "./script" you are missing the listening port again.

Here is a full example that works:

The script:

I was in the same situation months back, As much I concluded from Your problem, I guess you are struggling to setup Django with React. I would like to share my implementation(it is a standard one everyone recommends to use it.)

Follow These Steps accordingly:-

1. Separate your Frontend with your Backend, What this means is You need to prepare the REST API as your backend Do not use Django templates just make a Restful API which returns some JSON data in every method of your views.py.You can Use DJANGO REST FRAMEWORK for making rest-API,it provides lots of functionalities,You will also need to install CORS-HEADERS by doing pip install django-cors-headers and update your INSTALLED_APPS in settings.py by:-

With --conf spark.pyspark.{} and export PYSPARK_PYTHON=/usr/local/bin/python2.7 you set options for your local environment / your driver. To set options for the cluster (executors) use the following syntax:

If you only want to use Django's ORM (no views, admin, templates), then yes, you can use Django ORM in AWS Lambda as a library and no need for Zappa.

You can see how to do it from here: Using only the DB part of Django

However, take note that in AWS Lambda, you are billed per 100ms of execution time and Django ORM is not exactly fast (vs. direct raw queries).

It is recommended that you keep your Lambdas as lean as possible. Loading up the entire Django package is opposite of that recommendation.

just define a collections key in your _config.yml:

Angular documentation isn't alwaays 'perfect' :). Here is a link that might help NPM Angular New Router

If a new table contains no data, its DataBodyRange is Nothing. When you add any data to the table, DataBodyRange is set to a range, and even if you delete the data later, it will remain initialized.

In your situation, the simplest solution might be to just test DataBodyRange before doing anything, i.e.,

You should use this custom plan file from Zeus. Save it as custom_plan.rb at the root of your application:

I am separating each AgreegateRoot into its own project

I wouldn't have a separate project for each AggregateRoot, this seems like overkill to me. What do you gain by this? You can just use a class / actor, no need for an entirely separate project.

It sounds like you might be getting confused by how to reference the C# types that represent your events, which isn't surprising if you have a separate project per AggregateRoot - you'll quickly run into circular references. Try starting with a single project where you separate bounded contexts using folders. In each folder, create any aggregates you need, and any events they are responsible for. This way, all actors can see all the event types. Once this grows / becomes unmanageable you can look at splitting it out into separate projects, something along the lines of:

• MyApp.BoundedContext1
• MyApp.BoundedContext1.Events
• MyApp.BoundedContext2
• MyApp.BoundedContext2.Events

Note that the events your actors produce and subscribe to represent a kind of public contract / API throughout the system. Having them as separate DLLs as above avoids circular references (as the .Events project don't reference anything). So in this structure, MyApp.BoundedContext1 can have a reference to MyApp.BoundedContext1.Events and publish them. MyApp.BoundedContext2 can also reference MyApp.BoundedContext1.Events and subscribe to them.

I want the event published by an Actor to be handled by Handlers (other Actors), of which current AggregateRoot Actor or Child Entity inside should have no knowledge.

This is where I am totally stuck. How is this achieved?

Your publisher does not need knowledge of subscribers. The publisher just publishes a message to the EventStream. The context that both the actor and event type are defined in should be the same (i.e. publishers should 'own' their event types). For example, if you have a ValidationActor that publishes ThingValidated events, they should both be in the same context.

subscriber in System.EventStream.Subscribe, is IActorRef. To get this I would need knowledge of the class.

Which class? The subscriber already has knowledge of itself. You can just use Self to get the IActorRef. If you mean the event class, then see above about how to structure your project to reference this.

Once an actor is created, it can register for any event types it is interested in - you can put this code in the initialisation code of the actor itself if you need, or if you have singleton-style actors, in some sort of bootstrapper function if you prefer.