mirror of
https://github.com/avinal/avinal.github.io.git
synced 2026-07-03 23:30:09 +05:30
@@ -0,0 +1,60 @@
|
||||
---
|
||||
date: 2019-09-21 15:47
|
||||
slug: for-sunshine
|
||||
category: article
|
||||
tags: [love, article, hindi]
|
||||
---
|
||||
# प्रेम रतन धन पायो
|
||||
|
||||
टूटता तारा देखना एक अलौकिक अनुभव है। हिमाद्रि के छत से आसमान कुछ ज्यादा ही करीब प्रतीत होता है । लोग सदियों से हिमालय को पूजते आयें हैं ।
|
||||
दादा-दादी कहा करते थे ये जिंदा पहाड़ हैं । सारी बातें सुनते हैं लोगों की । उनके दुख दर्द दूर करते हैं, ये देवता हैं । आजकल जब रोज़ क्लास
|
||||
आते जाते दूर पहाड़ों की चोटियाँ देखता हूँ तो उनकी विशालता का अनुभव होता हैं । एक पल को अगर ये मान लिया जाए की हमारी सारी धार्मिक किताबें
|
||||
वो कहानियाँ हैं जो पथिक लेखकों के द्वारा लिखी गयी हैं तो सारी बातें साफ हो जाती है कि क्यूँ देवी-देवताओं ने हिमालय को अपनाया है। टूटता
|
||||
तारा देखना अलौकिक है पर हिमालय की श्रेणियों से टूटता तारा देखना दैविक है । और वो कहते हैं न जिसमें न कोई तर्क हो न ही हाथों की सफाई वो
|
||||
दैविक है। टूटते तारो के बारे में लोगों के बहुत सारे विश्वास हैं । कभी विभीषिका का पूर्वाभास माने जाने वाले इन टूटते तारे आज इच्छा पूरक के
|
||||
प्रतीक हैं । कुछ लोगों का ये भी मानना है कि टूटते तारे दिवंगत लोगों का संकेत हैं । हिमालय की कन्दराओं में न जाने कितने ही ऋषि-मुनियों ने
|
||||
तप करते हुए अपना जीवन अर्पित कर दिया । इसलिए हिमालय की पहाड़ों से टूटता तारा देखना दैविक हैं क्योंकि शायद वो तारे उन ऋषि-मुनियों की पवित्र
|
||||
आत्माओं का संकेत हैं ।
|
||||
|
||||
प्रकृति की सुंदरता और कलाकारी हिमालय की कण-कण में झलकती है। प्रकृति ने प्रेम को भी हिमालय के जितना ही विशाल और अलौकिक बनाया है । ये एक
|
||||
अलग चर्चा का विषय है कि हिमालय पहले आया या प्रेम। मैं तो प्रेम के पक्ष में हूँ । वो हर अणु-परमाणु जिन्होंने इतने बड़ा पहाड़ खड़ा किया वो सब
|
||||
आपस में प्रेम से बंधे हुए हैं। ये पृथ्वी, सूर्य, चंद्रमा, आकाश-गंगा इत्यादि सब प्रेम से बंधे हुए हैं । और हिमाद्रि के छत पर मैं इसी प्रेम
|
||||
के आगोश में आकर भावशून्य होकर तारों को निहार रहा था । तभी मानो सदियों की मन्नत पूरी हुई और मुझे एक टूटता तारा दिखा । आप मेरी स्थिति की
|
||||
जटिलता का अनुभव इस प्रकार से लगा सकते हैं कि लोग टूटते तारे से मन्नत मांगते हैं और मैं टूटता तारा ही मन्नत में मांग रहा था । इससे पहले की
|
||||
मैं पिछली जटिलता से बाहर आता की दूसरी जटिलता सामने आ पड़ी की तारा तो दिख गया पर मैं माँगूँ क्या ? और अगर आप सोच रहे की भाई पैसे मांग लो
|
||||
शोहरत , नाम , शक्ति और पता नहीं क्या-क्या ? मांग तो लेता पर अगर आप मेरी जगह इसी स्थिति में होते तो शायद आपको भी ये सब याद न आता । तो मैं
|
||||
एक पल को ये आकलन करने लगा की क्या कुछ ऐसा है जिसकी मुझे बहुत जरूरत है पर मेरे पास हो नहीं । और आपको पता है की गहरी सोच में जाने पर अक्सर
|
||||
क्या होता है। अब वो लोग जो ये सोच रहे की भाईसाब आप हर कहानी(सच्ची घटना का विवरण वाली कहानी 😊) में सो क्यूँ जाते हैं। सच बताऊँ तो इसका
|
||||
कोई सटीक जबाव नहीं है मेरे पास, पर अध्यात्म ये कहता है की जब आप सो रहे होते हैं तो आपका मन चेतना के कई स्थिति से गुजरता है। जब आप परम
|
||||
चैतन्य अवस्था में होते हैं तो रहस्य, प्रतिभज्ञान इत्यादि के रास्ते खुल जाते हैं। और विज्ञान ये भी कहता है कि निद्रा के माध्यम से इस
|
||||
अवस्था में जाना उतना ही अनिश्चित है जितना किसी बाला का मेरे लिए प्रेम-प्रस्ताव । सरल शब्दों में – मैं कुछ समय के लिए सो गया।
|
||||
|
||||
आज से ठीक 2 महीने पहले अगर ये मुझसे कोई पूछता की क्या चाहिए तुम्हें तो शायद मेरे पास जबाव होता। दोस्त तो बहुत हैं पर जब कोई ऐसा हो जो
|
||||
आपके अधूरे वाक्य पूरे कर सके, कोई ऐसा जो आपकी भावनाओं को आपकी तरह समझ सके, कोई ऐसा जो आपको आपके असल रूप में पसंद करता हो । आपको लग रहा
|
||||
होगा की मैं एक प्रेमिका का विवरण दे रहा हूँ, पर नहीं या शायद हाँ , मैं समझता हूँ की अधिकतर लोग प्रेमिका शब्द का प्रयोग अनुचित ढंग से करते
|
||||
हैं। जहां प्रेम है वहाँ प्रेमी-प्रेमिका होंगे फिर वो भाई-बहन का रिश्ता हो या माँ-बेटे का । एक पल को सोचो तो ऊपर के विवरण के लिए कोई सबसे
|
||||
सटीक उत्तर है तो वो है माँ। जब आप उन माँ-बाप जिन्होंने आपको जन्म दिया, आपका पालन-पोषण किया , आपको इस लायक बनाया कि आप इस वक़्त ये लेख पढ़
|
||||
पा रहे हैं , उनको अपनी प्रेमी-प्रेमिका नहीं कह सकते तो शायद किसी और लड़के-लड़की को कहने का आपको कोई हक़ नहीं है। पर ये बात निजी समझदारी की
|
||||
है और मैं माँ-बाप के बारे में बिलकुल भी बात नहीं कर रहा, इन 2-4 पन्ने में उनको चित्रित कर पाना दुष्कर है। अगर माँ है तो ये अलग व्यक्ति
|
||||
क्यूँ ? लोग कहते हैं क्योंकि भगवान हर जगह नहीं हो सकते इसलिए उन्होंने माँ बनाई। पर मैं कहता हूँ माँ भी हर जगह नहीं हो सकती इसलिए भगवान ने
|
||||
दोस्त बनाए और विशेष लोग भी बनाए। आज तक बहुत सारे लोग आए-गए , कई बार लगा की शायद वो विशेष व्यक्ति मिलने ही वाला है पर वो भ्रम था शायद ये
|
||||
भी हो। मैं ये नहीं कह सकता की मेरी खोज पूर्ण हो गयी पर हाँ एक पड़ाव तो जरूर आ गया है। उस पहली मुलाक़ात में एक पल को ऐसा लगा मानो किसी
|
||||
चमत्कारी दर्जी ने कपड़े की जगह एक पूरा आदमी सिल कर दिया हो। सब कुछ एकदम नाप के अनुरूप। शायद कई सालों के बाद मैं खुशियों का बवंडर अपने अंदर
|
||||
महसूस कर रहा था। आप पूछेंगे इसमें प्रेम कहाँ है? हिमालय जितना विशाल है उतना ही गहरा भी है , यहाँ भी प्रेम गहराई में है । प्रेम का होना
|
||||
जरूरी है दिखावा तो हर कोई कर लेता है। कबीर ने अपने एक दोहे में कहा है :
|
||||
|
||||
**बूंद समानी समूंद में , जानत है सब कोई; समूंद समाना बूंद में , बूझे बिरला कोई।**
|
||||
|
||||
मैं इस दोहे को प्रेम के संदर्भ में व्याख्या करना चाहूँगा। लोग बूंद हैं और प्रेम समुद्र, लोगों को प्रेम में पड़ते सबने देखा है या सुना है,
|
||||
पर जो प्रेम लोगों के अंदर व्याप्त है ये हर कोई नहीं समझता। मैं उस विशेष व्यक्ति का कृतज्ञ हूँ जिसने ने मुझे इस दोहे के मूल भाव का अहसास
|
||||
करवाया।
|
||||
|
||||
कभी-कभी डर लगता है, खोने का उसे। आजकल दुनिया में सब अनिश्चित है। कब-क्या हो जाए ये कोई नहीं बता सकता। पहले सिर्फ पृथ्वी थी फिर लोग हुए और
|
||||
तब से पृथ्वी अस्थमा की मरीज है। किसी प्रसिद्ध कवि ने लिखा है :
|
||||
|
||||
**आज आदमी में विष इतना भर गया है, की विषधरों का वंश उनसे डर गया है,**
|
||||
**कल को कहते सुनोगे , आदमी काटा और साँप मर गया है।**
|
||||
|
||||
ठंडी-ठंडी हवाओं ने मेरी सारी नींद उड़ा दी। प्रकृति शायद मुझे खुश करके मारना चाहती थी। आसमान ने एक बड़े काले पर्दे का रूप ले लिया था और उस
|
||||
पर्दे पर दसियो उजले साँप रेंगते नज़र आ रहे थे। मानो दस सालो के टूटते तारे एक साथ दिख रहे हों और आसमान कह रहा हो – जो चाहिए, जितना चाहिए
|
||||
माँग लो। और मैंने सच में माँग लिए , लगभग सब कुछ । और उसको हमेशा पास रखने की दुआ तो नहीं माँग सका , पर वो जहां रहे, खुश रहे, सलामत रहे।
|
||||
@@ -0,0 +1,89 @@
|
||||
---
|
||||
date: 2021-01-04 21:47
|
||||
tags: [HRT, hudsonrivertrading, interview, internship]
|
||||
slug: hrt-interview-1
|
||||
category: blog
|
||||
---
|
||||
|
||||
# `HRT (Hudson River Trading)` Systems Internship Interview Experience
|
||||
|
||||
I applied for **Systems Internship - Summer 2021** back in December 2020
|
||||
at [Hudson River Trading](https://www.hudsonrivertrading.com) , New
|
||||
York. The internship description was: -
|
||||
|
||||
> We are looking for highly motivated students who are eager to learn
|
||||
> and excited about systems to join us for our summer internship
|
||||
> program. As a systems intern, you may have the opportunity to work on
|
||||
> projects in the following areas:
|
||||
>
|
||||
> - Programming/scripting (Golang, Python, C++, C)
|
||||
> - FOSS development
|
||||
> - HPC, Cluster computing
|
||||
> - System Administration
|
||||
> - Linux, Debian
|
||||
> - Linux-based computer security
|
||||
> - Data Storage
|
||||
> - Large deployment or config management
|
||||
|
||||
The first step was a coding test on the Codility platform. If you have
|
||||
used any of the online coding platforms, this is similar. It was a
|
||||
`2.5 hrs (90 mins)` test consisting of 3 questions. They let you use
|
||||
`online references (documentation, man pages, etc.)` but **do not copy
|
||||
the code** as it will highly reduce your chances of qualifying for this
|
||||
first stage. You can choose between **C/C++**, **Python** and **Golang**
|
||||
(no Java 😪).
|
||||
|
||||
Questions were clear and of medium level. But they were designed in such
|
||||
a way that you must know the basics before you could attempt. Also, they
|
||||
expected a clear and concise approach. Two of the most important points
|
||||
in their instructions were: -
|
||||
|
||||
> - While correctness and performance are the most important factors
|
||||
> for evaluation, we will take test duration into account as well.
|
||||
> - Please understand that this test is meant to be challenging. A
|
||||
> perfect score is not necessary to move on to future interview
|
||||
> rounds, so do the best you can!
|
||||
|
||||
So, you must be near perfect in your approach as well as on time. I did
|
||||
them kind of quickly. They will show you a summary of your submission
|
||||
but not the results. It will take almost 2 weeks to get back to you for
|
||||
further steps.
|
||||
|
||||
Next, I received a mail invitation for a telephonic interview. **This
|
||||
interview will last about 45 minutes and will be technical but will not
|
||||
require coding. Interview topics may include your background,
|
||||
programming languages, and Unix/Linux concepts**. Once you receive this
|
||||
mail you can then decide a time slot for an interview.
|
||||
|
||||
I was not sure what they will ask if this is not a coding interview. The
|
||||
interviewer was very polite, and he was explaining the questions too.
|
||||
Questions were not so tricky but practical and real-life. Since it was
|
||||
**not for SDE role**, the questions were mostly related to Linux/Unix,
|
||||
C++ (mainly pointers and memory), Python/Bash scripting, automation,
|
||||
knowledge of tools (IDEs, Editors, System Administration Tools) and
|
||||
previous experiences. The interview would often explain why he is asking
|
||||
this question, this was very nice. Then some common interview questions,
|
||||
why do you want to work for this role? What makes you fit for this role?
|
||||
etc.
|
||||
|
||||
One thing that I want to point out is that the interviewer was
|
||||
repeatedly checking my resume, and for the most part he did not ask
|
||||
anything that was not on my resume. So, my tip is to create a nice
|
||||
resume with genuine work/tool experiences. And when you are applying for
|
||||
such a role, it would be helpful if you mention mathematics or other
|
||||
courses that you have taken. *Do not lie on your resume*. They will
|
||||
easily catch that.
|
||||
|
||||
The other thing is to keep your words short and clear; I was not great
|
||||
at communication, but you can be. If the interviewer allows then use
|
||||
examples for the things you cannot explain. I used nice examples. At
|
||||
last, he gave me short feedback on how well I performed.
|
||||
|
||||
At last, I want to point out things I should not have done. The first
|
||||
is, I did not ask much about the role, you must do this at least once.
|
||||
Second, I am talkative, I do not know if the interviewer was not faking
|
||||
his expressions (because he would often discuss in-depth), but not all
|
||||
interviewers will be the same. So, do not talk too much, nor too less.
|
||||
At last work on your communication skill, mostly how you to present
|
||||
things and how to answer technical as well as behavioral questions. I
|
||||
was not fluent, but my way of presentation might have saved me.
|
||||
@@ -0,0 +1,208 @@
|
||||
---
|
||||
title: Developing Minimal Tekton Server
|
||||
date: 2022-02-27 20:47
|
||||
modified: 2022-03-07 22:47
|
||||
category: development
|
||||
tags: [tekton, go, kubernetes, openshift, redhat, intern, golang, openshift-pipelines]
|
||||
---
|
||||
|
||||
# Developing Minimal Tekton Server [<img src="/images/mks_logo.png" class="align-middle" style="width:1.5em"
|
||||
|
||||
This blog is a descreptive account of the development of Minimal Tekton Server.
|
||||
This is highly technical in nature, so please make sure that you have sufficient
|
||||
knowledge about Golang, Docker, Kubernetes and TektonCD. You can refer to my
|
||||
[previous blog]("https://avinal.space/posts/development/i-am-loving-it-redhat.html")
|
||||
to know about these topics.
|
||||
|
||||
As mentioned in my last blog, we were given to implement an application
|
||||
named **Minimal Tekton Server**. The problem statement reads:
|
||||
|
||||
> We will be designing and implementing an application that will be
|
||||
> talking to Tekton APIs to create resources on a Kubernetes/OpenShift
|
||||
> Cluster. The application will expose some fields of the Tekton
|
||||
> Resources which the user will provide and then this application will
|
||||
> create Tekton resources by talking to Tekton APIs available on the
|
||||
> cluster to create the resources based on the user-provided fields.
|
||||
|
||||
There are three parts in this project for the application and two more
|
||||
parts for the CI/CD using TektonCD and Kubernetes/OpenShift. I will go
|
||||
through each part descriptively and try to explain what we did.
|
||||
|
||||
## The Architecture of MKS
|
||||
|
||||
The first task in the development of the Minimal Tekton Server was
|
||||
creating its architectural diagram. Our first diagram was trash compared
|
||||
to the final diagram. Yeah, we learned. I will be explaining our
|
||||
final(obviously) architectural diagram and try to make some sense out of
|
||||
band-aids and duct tapes.
|
||||
|
||||
<img src="/images/mks-architecture.png"
|
||||
class="img-fluid my-3 img-fluid my-3" alt="The MKS Arhitecture" />
|
||||
|
||||
Let me start with explaining **What are MKS Resources?**. I hope you
|
||||
know at least tidbits about Kubernetes and by the definition: *A
|
||||
resource is an endpoint in the Kubernetes API that stores a collection
|
||||
of API objects of a certain kind; for example, the built-in
|
||||
:code:\`pods\` resource contains a collection of Pod objects.* But
|
||||
developers soon realized that these in-built resources were not enough
|
||||
for the ever-growing applications of Kubernetes. Here [custom
|
||||
resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
||||
comes into the picture. *A custom resource is an extension of the
|
||||
Kubernetes API that is not necessarily available in a default Kubernetes
|
||||
installation.* To define a custom resource we use something called
|
||||
[Custom Resource
|
||||
Definition](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/).
|
||||
So MKS Resources are such custom resources that correspond to the
|
||||
TektonCD custom resources.
|
||||
|
||||
<img src="/images/venus-flytrap.gif"
|
||||
class="float-md-right ml-3 float-md-right ml-3" width="250"
|
||||
alt="A venus flytrap engulphing an insect." />
|
||||
|
||||
Let us now focus on the box containing `Controller` and `API server`.
|
||||
The controller can be said as a stimulus-response mechanism. Take the
|
||||
analogy of a Venus Flytrap plant. The trap is initially open. There are
|
||||
`trigger` hairs on the inside of the trap. Once an insect is detected,
|
||||
there is a change of state and the trap closes in a blick on the eye.
|
||||
The controller works the same way. It listens for the change in the
|
||||
state of the MKS resources and immediately transfers the request to the
|
||||
Tekton API to reflect the change in the corresponding Tekton resources.
|
||||
The changes can be creation, deletion, or updating. The API server
|
||||
ensures that there is a working connection between our controller and
|
||||
the Tekton API.
|
||||
|
||||
MKS Server also exposes APIs to introduce a change of state in the MKS
|
||||
resources. In technical terms these are called `verbs`. There are five
|
||||
such verbs that we have exposed: `create`, `update`, `get`, `delete`,
|
||||
and `list`. They can be utilized by a REST client, or in our case **MKS
|
||||
CLI** to introduce desired change. The MKS command-line interface
|
||||
provides commands and subcommands to do the desired tasks.
|
||||
|
||||
Whenever there is a change in the state, there is a logic running inside
|
||||
the controller to react on that and that also affects our database. We
|
||||
store four datapoints in our database: `created`, `deleted`,
|
||||
`completed`, and `failed`. They tell us about the current statistcs of
|
||||
our MKS resource using a single-page web app called **MKS Dashboard**
|
||||
(or UI).
|
||||
|
||||
This was about the architecture of the Minimal Tekton Server. Let us
|
||||
jump into more technical stuff.
|
||||
|
||||
## How to implement a CRD controller?
|
||||
|
||||
During this assignment, something that took the most time and effort was
|
||||
the implementation of a controller for our custom resources. This isn't
|
||||
very hard if you go by the rules and do the things according to the
|
||||
well-defined documents and blogs since this is a standard step in the
|
||||
implementation of any custom resource controller. But did we follow the
|
||||
rules? Hell no! But this time, let us go step-by-step.
|
||||
|
||||
1. The first step is to define a `CustomResourceDefinition` for our custom
|
||||
resource. Let us define a CRD called `spacetime`. To do this you can write a
|
||||
YAML file like below.
|
||||
|
||||
``` yaml
|
||||
# file: spacetime-crd.yaml
|
||||
apiVersion: apiextensions.k8s.io/v1
|
||||
kind: CustomResourceDefinition
|
||||
metadata:
|
||||
# name must match the spec fields below, and be in the form: <plural>.<group>
|
||||
name: spacetimes.example.com
|
||||
spec:
|
||||
# group name to use for REST API: /apis/<group>/<version>
|
||||
group: example.com
|
||||
# list of versions supported by this CustomResourceDefinition
|
||||
versions:
|
||||
- name: v1alpha1
|
||||
# Each version can be enabled/disabled by Served flag.
|
||||
served: true
|
||||
# One and only one version must be marked as the storage version.
|
||||
storage: true
|
||||
schema:
|
||||
openAPIV3Schema:
|
||||
type: object
|
||||
properties:
|
||||
spec:
|
||||
type: object
|
||||
properties:
|
||||
message:
|
||||
type: string
|
||||
# either Namespaced or Cluster
|
||||
scope: Namespaced
|
||||
names:
|
||||
# plural name to be used in the URL: /apis/<group>/<version>/<plural>
|
||||
plural: spacetimes
|
||||
# singular name to be used as an alias on the CLI and for display
|
||||
singular: spacetime
|
||||
# kind is normally the CamelCased singular type. Your resource manifests use this.
|
||||
kind: SpaceTime
|
||||
# shortNames allow shorter string to match your resource on the CLI
|
||||
shortNames:
|
||||
- st
|
||||
```
|
||||
|
||||
You can learn more about the fields and options
|
||||
[here](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/).
|
||||
The CRD that we defined above corresponds to the `CustomResource` given
|
||||
below. Once you apply the above file you will be able to see the
|
||||
`spacetime` custom resource on your Kubernetes/OpenShift cluster.
|
||||
|
||||
``` yaml
|
||||
# file: spacetime-cr.yaml
|
||||
apiVersion: spacetimes.example.com/v1alpha1
|
||||
kind: SpaceTime
|
||||
metadata:
|
||||
name: spacetime-cr
|
||||
spec:
|
||||
message: "Hello from space!"
|
||||
```
|
||||
|
||||
Apply them using the following commands:
|
||||
|
||||
``` bash
|
||||
kubectl apply -f spacetime-crd.yaml
|
||||
kubectl apply -f spacetime-cr.yaml
|
||||
```
|
||||
|
||||
1. Once we have defined our custom resources, we need to define the
|
||||
types that will correspond to this custom resource definition. This
|
||||
can be done using `k8s.io/apimachinery/pkg/apis/meta/v1` package
|
||||
written in golang. Did I tell you that this is all in golang? Well,
|
||||
now you know. Create a package structure for a golang project and
|
||||
add the definition of the type as given below.
|
||||
|
||||
``` bash
|
||||
mkdir -p pkg/api/spacetime/v1alpha1
|
||||
touch pkg/api/spacetime/v1alpha1/{spacetime_types,register,doc}.go pkg/api/spacetime/register.go
|
||||
```
|
||||
|
||||
Add the following content to the corresponding files.
|
||||
|
||||
``` golang
|
||||
// file: /pkg/api/spacetime/v1alpha1/spacetime_types.go
|
||||
package v1alpha1
|
||||
|
||||
import (
|
||||
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
|
||||
)
|
||||
|
||||
type SpaceTime struct {
|
||||
metav1.TypeMeta `json:",inline"`
|
||||
metav1.ObjectMeta `json:"metadata,omitempty"`
|
||||
|
||||
Spec SpaceTimeSpec `json:"spec"`
|
||||
}
|
||||
|
||||
type SpaceTimeSpec struct {
|
||||
Message string `json:"message"`
|
||||
}
|
||||
|
||||
type SpaceTimeList struct {
|
||||
metav1.TypeMeta `json:",inline"`
|
||||
metav1.ListMeta `json:"metadata"`
|
||||
|
||||
Items []SpaceTime `json:"items"`
|
||||
}
|
||||
```
|
||||
|
||||
### To be Continued
|
||||
@@ -0,0 +1 @@
|
||||
# This page does not exists
|
||||
@@ -943,18 +943,18 @@ q:before {
|
||||
font-family: 'Share Tech Mono';
|
||||
font-style: normal;
|
||||
font-weight: 400;
|
||||
src: url('fonts/share-tech-mono-v15-latin-regular.eot');
|
||||
src: url('/website/fonts/share-tech-mono-v15-latin-regular.eot');
|
||||
/* IE9 Compat Modes */
|
||||
src: local(''),
|
||||
url('fonts/share-tech-mono-v15-latin-regular.eot?#iefix') format('embedded-opentype'),
|
||||
url('/website/fonts/share-tech-mono-v15-latin-regular.eot?#iefix') format('embedded-opentype'),
|
||||
/* IE6-IE8 */
|
||||
url('fonts/share-tech-mono-v15-latin-regular.woff2') format('woff2'),
|
||||
url('/website/fonts/share-tech-mono-v15-latin-regular.woff2') format('woff2'),
|
||||
/* Super Modern Browsers */
|
||||
url('fonts/share-tech-mono-v15-latin-regular.woff') format('woff'),
|
||||
url('/website/fonts/share-tech-mono-v15-latin-regular.woff') format('woff'),
|
||||
/* Modern Browsers */
|
||||
url('fonts/share-tech-mono-v15-latin-regular.ttf') format('truetype'),
|
||||
url('/website/fonts/share-tech-mono-v15-latin-regular.ttf') format('truetype'),
|
||||
/* Safari, Android, iOS */
|
||||
url('fonts/share-tech-mono-v15-latin-regular.svg#ShareTechMono') format('svg');
|
||||
url('/website/fonts/share-tech-mono-v15-latin-regular.svg#ShareTechMono') format('svg');
|
||||
/* Legacy iOS */
|
||||
}
|
||||
|
||||
|
||||
+2
-2
@@ -5,8 +5,8 @@
|
||||
<meta charset="UTF-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<link rel="stylesheet" href="/website/foo-style.css">
|
||||
<link rel="stylesheet" href="/website/mdn-style.css">
|
||||
<link rel="stylesheet" href="/website/foo-style.css">
|
||||
|
||||
<title>Document</title>
|
||||
<script src="/website/redirect.js"></script>
|
||||
@@ -23,7 +23,7 @@
|
||||
<script src="/website/prism.js"></script>
|
||||
<script src="https://cdn.jsdelivr.net/npm/prismjs@1.29.0/plugins/autoloader/prism-autoloader.min.js"></script>
|
||||
<script>
|
||||
var app = Elm.Blog.init({ node: document.getElementById("app") });
|
||||
var app = Elm.Main.init({ node: document.getElementById("app") });
|
||||
|
||||
app.ports.sendString.subscribe(function (markdowndata) {
|
||||
|
||||
|
||||
+1
-1
@@ -252,7 +252,7 @@ updateUrl model =
|
||||
|> toBlog model
|
||||
|
||||
Just (BlogPost category slug) ->
|
||||
Blog.init (Just (category ++ slug))
|
||||
Blog.init (Just (category ++ "/" ++ slug))
|
||||
|> toBlog model
|
||||
|
||||
Just Terminal ->
|
||||
|
||||
Reference in New Issue
Block a user